July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1183123] systemd, NetworkManager and nscd - nfs mounts are failing
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1183123 https://bugzilla.suse.com/show_bug.cgi?id=1183123#c9 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NORESPONSE Status|NEW |RESOLVED --- Comment #9 from Jonathan Kang <songchuan.kang(a)suse.com> --- Closing this as RESOLVED NORESPONSE. Feel free to re-open it with requested information. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217309] New: [RPi4] rebootmgr does not reboot the system
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1217309 Bug ID: 1217309 Summary: [RPi4] rebootmgr does not reboot the system Classification: openSUSE Product: openSUSE Leap Micro Version: 5.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: lubos.kocman(a)suse.com Reporter: mbrugger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to reboot the system, system services is shut down but no reboot happens. That leaves the system in a state without networking. > printi:~ # rebootmgrctl get-strategy > Reboot strategy: best-effort > printi:~ # rebootmgrctl get-window > Maintenance window is set to *-*-* 03:30:00, lasting 01h30m. > printi:~ # rebootmgrctl is-active > RebootMgr is active journalctl output can be found here: https://paste.opensuse.org/pastes/c0c9f158cadd Interestingly running > rebootmgrctl reboot now does actually reboot the system. -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1227389] New: PackageKit kernel update is successful but kernel is not updated
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227389 Bug ID: 1227389 Summary: PackageKit kernel update is successful but kernel is not updated Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://openqa.opensuse.org/tests/4315791/modules/upda tes_packagekit_gpk/steps/253 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: songchuan.kang(a)suse.com Reporter: jpupava(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Created attachment 875874 --> https://bugzilla.suse.com/attachment.cgi?id=875874&action=edit 1. gpk-update-viewer --verbose as user ## Observation Test does rerun gpk-update-viewer until there is no update, but now it is stuck on this kernel update. PackageKit does update kernel-default* packages, there is pop-up "All updates were installed successfully", but when gpk-update-viewer is run again the same kernel update is there to update. Endless loop, I guess it should require reboot because zypper does have this note "Note: System reboot required." To get some logs I run 1. gpk-update-viewer --verbose as user, see gpk1.log 2. gpk-update-viewer --verbose as user, see gpk2.log 3. zypper -n up as root, see zypper.log 4. gpk-update-viewer --verbose as user, see gpk3.log https://openqa.opensuse.org/tests/4315791/modules/updates_packagekit_gpk/st… ## Reproducible Fails since (at least) Build [20240625-3](https://openqa.opensuse.org/tests/4297876) ## Expected result Last good: [20240625-2](https://openqa.opensuse.org/tests/4296612) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1227317] Can't turn off tap to click on trackpad
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227317 https://bugzilla.suse.com/show_bug.cgi?id=1227317#c4 --- Comment #4 from xiaoguang wang <xiaoguang.wang(a)suse.com> --- Thanks for the explanation. I haven't used this type of touch pad before. I think the system treats these 3 virtual buttons as real buttons, so disabling the tap to click didn’t work on these 3 virtual buttons. If just disabling the paste function of middle button, try this solution: 1.Install gnome-tweak package > zypper in gnome-tweaks 2.Open tweaks -> Mouse & Touchpad, disable ‘Middle Click Paste’ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227415] "Verifiying shim SBAT data failed" Error On First Reboot After Leap 15.6 Install
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227415 https://bugzilla.suse.com/show_bug.cgi?id=1227415#c1 hui <sturm-fr(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #1 from hui <sturm-fr(a)web.de> --- . *** This bug has been marked as a duplicate of bug 1209985 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209985] Secure boot violation when install Leap shim and Tumbleweed shim in one machine
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1209985 https://bugzilla.suse.com/show_bug.cgi?id=1209985#c56 hui <sturm-fr(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |www(a)vcnet.com --- Comment #56 from hui <sturm-fr(a)web.de> --- *** Bug 1227415 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227158] VUL-0: CVE-2024-24792: TRACKERBUG: golang.org/x/image/tiff: parsing of a corrupt or malicious image with invalid color indices can cause a panic
by bugzilla_noreply＠suse.com 04 Jul '24

04 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227158 https://bugzilla.suse.com/show_bug.cgi?id=1227158#c6 --- Comment #6 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1227158) was mentioned in https://build.opensuse.org/request/show/1185695 Factory / keybase-client -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224364] btrfsmaintenance 0.5.1: openqa test failing at "btrfs scrub status"
by bugzilla_noreply＠suse.com 04 Jul '24

04 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1224364 https://bugzilla.suse.com/show_bug.cgi?id=1224364#c1 --- Comment #1 from David Sterba <dsterba(a)suse.com> --- Fixed in version 0.5.2, sent as SR 1185448. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225636] New: Facetimehd firmware/driver fails to load
by bugzilla_noreply＠suse.com 04 Jul '24

04 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225636 Bug ID: 1225636 Summary: Facetimehd firmware/driver fails to load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: crdcastro5(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hardware is a late 2015 11" Macbook Air. The facetimehd-kmp-default package was installed by default and I installed the facetimehd-firmware manually, despite this the driver fails to load and the camera is not detected as a device. [I] clayton@s-169-232-95-114 ~> dmesg -w | grep facetimehd [ 2.934906] [ T349] facetimehd 0000:02:00.0: Found FaceTime HD camera with device id: 1570 [ 2.937304] [ T349] facetimehd 0000:02:00.0: Setting 64bit DMA mask [ 2.958735] [ T349] facetimehd 0000:02:00.0: S2 PCIe link init succeeded [ 2.958770] [ T349] facetimehd 0000:02:00.0: Refclk: 25MHz (0xa) [ 2.968787] [ T349] facetimehd 0000:02:00.0: PLL reset finished [ 2.968793] [ T349] facetimehd 0000:02:00.0: Waiting for S2 PLL to lock at 450 MHz [ 2.968808] [ T349] facetimehd 0000:02:00.0: S2 PLL is locked after 10 us [ 2.978828] [ T349] facetimehd 0000:02:00.0: S2 PLL is in bypass mode [ 2.998898] [ T349] facetimehd 0000:02:00.0: DDR40 PHY PLL locked on safe settings [ 2.998916] [ T349] facetimehd 0000:02:00.0: STRAP valid [ 2.998917] [ T349] facetimehd 0000:02:00.0: Configuring DDR PLLs for 450 MHz [ 2.998925] [ T349] facetimehd 0000:02:00.0: DDR40 PLL is locked after 0 us [ 2.998935] [ T349] facetimehd 0000:02:00.0: First DDR40 VDL calibration completed after 2 us [ 2.998943] [ T349] facetimehd 0000:02:00.0: Second DDR40 VDL calibration completed after 1 us [ 2.998944] [ T349] facetimehd 0000:02:00.0: Using step size 144 [ 2.998950] [ T349] facetimehd 0000:02:00.0: VDL set to: coarse=0x10008, fine=0x10119 [ 2.998955] [ T349] facetimehd 0000:02:00.0: Virtual VTT enabled [ 3.019479] [ T349] facetimehd 0000:02:00.0: S2 DRAM memory address: 0x22159559 [ 3.019496] [ T349] facetimehd 0000:02:00.0: Rewrite DDR mode registers succeeded [ 3.019719] [ T349] facetimehd 0000:02:00.0: Full memory verification succeeded! (0) [ 3.019942] [ T349] facetimehd 0000:02:00.0: Direct firmware load for facetimehd/firmware.bin failed with error -2 [ 3.020079] [ T349] facetimehd 0000:02:00.0: probe with driver facetimehd failed with error -2 I force reinstalled both and rebooted but still saw the same behavior. additional context: uname -a Linux localhost.localdomain 6.9.1-1-default #1 SMP PREEMPT_DYNAMIC Fri May 17 11:59:46 UTC 2024 (0c0b0b5) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1225299] systemd-boot doesn't display passphrase prompt for decryption until a key is pressed
by bugzilla_noreply＠suse.com 04 Jul '24

04 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225299 https://bugzilla.suse.com/show_bug.cgi?id=1225299#c5 --- Comment #5 from David B <db(a)mail25.net> --- (In reply to Alberto Planas Dominguez from comment #4) > You mean that you installed Plymouth later? No, it was preinstalled if I remember right. I selected the "Desktop with KDE Plasma" and didn't change any of the packages. So, after OS installation Plymouth didn't seem to be set up for the kernel that came with the OS installation. After updating to the latest snapshot which had a new kernel version Plymouth seems to work how it should for that new kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 0