October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224068] New: Budgie crashes session if it crashes twice
by bugzilla_noreply＠suse.com 05 Oct '24

05 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1224068 Bug ID: 1224068 Summary: Budgie crashes session if it crashes twice Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: asdhio(a)tuta.io QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874777 --> https://bugzilla.suse.com/attachment.cgi?id=874777&action=edit A screen saying "Oh no! Something has gone wrong." Budgie will throw a screen "Oh no! Something has gone wrong." if Budgie crashes more than one time. A common case of it happening is if Bugdie panel crashes more than once. The likelihood of such crashes can be increased if budgie-appmenu-applet or any applets from budgie-extras are applied. The problem is that Budgie won't just restart its panels and let the user do their job (like XFCE and MATE would). Budgie will stop after second crash even though those applications are still running. But Budgie gives no option other than to log out. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1230779] Update nvidia driver to latest 550.120 release
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230779 https://bugzilla.suse.com/show_bug.cgi?id=1230779#c12 --- Comment #12 from Jens Hoffmann <jens_hoffmann_(a)web.de> --- note: Solution from https://bugzilla.opensuse.org/show_bug.cgi?id=1231227 does not work -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230779] Update nvidia driver to latest 550.120 release
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230779 https://bugzilla.suse.com/show_bug.cgi?id=1230779#c11 --- Comment #11 from Jens Hoffmann <jens_hoffmann_(a)web.de> --- Status Operating System: openSUSE Tumbleweed-Slowroll 20240901 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.11-1-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i5-10600K CPU @ 4.10GHz Memory: 15.4 GiB of RAM Graphics Processor: llvmpipe Manufacturer: CSL-Computer GmbH & Co. KG Product Name: 859 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230779] Update nvidia driver to latest 550.120 release
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230779 https://bugzilla.suse.com/show_bug.cgi?id=1230779#c10 --- Comment #10 from Jens Hoffmann <jens_hoffmann_(a)web.de> --- ~> rpm -qa | grep nvidia libnvidia-egl-wayland1-1.1.16-1.1.x86_64 nvidia-video-G06-550.120-27.1.x86_64 nvidia-compute-utils-G06-550.120-27.1.x86_64 nvidia-texture-tools-2.1.2-2.13.x86_64 nvidia-compute-G06-550.120-27.1.x86_64 nvidia-compute-G06-32bit-550.120-27.1.x86_64 nvidia-utils-G06-550.120-27.1.x86_64 nvidia-gl-G06-550.120-27.1.x86_64 kernel-firmware-nvidia-20240913-1.1.noarch libnvidia-egl-wayland1-32bit-1.1.16-1.1.x86_64 nvidia-gl-G06-32bit-550.120-27.1.x86_64 pcp-pmda-nvidia-gpu-6.2.1-1.2.x86_64 nvidia-video-G06-32bit-550.120-27.1.x86_64 nvidia-driver-G06-kmp-default-550.120_k6.10.9_1-27.1.x86_64 Info: secure boot MOK endrolld -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230779] Update nvidia driver to latest 550.120 release
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230779 https://bugzilla.suse.com/show_bug.cgi?id=1230779#c8 Jens Hoffmann <jens_hoffmann_(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jens_hoffmann_(a)web.de --- Comment #8 from Jens Hoffmann <jens_hoffmann_(a)web.de> --- Operating System: openSUSE Tumbleweed-Slowroll 20240901 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.11-1-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i5-10600K CPU @ 4.10GHz Memory: 15.4 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3050/PCIe/SSE2 Manufacturer: CSL-Computer GmbH & Co. KG Product Name: 859 after update via zypper dup Nvidia driver 550.120 driver (repo-non-free) cannot be loaded journalctl --system -S 2024-10-04 ..... Okt 04 19:07:50 localhost.localdomain kernel: NVRM: API mismatch: the client has the version 550.120, but NVRM: this kernel module has the version 550.107.02. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. Okt 04 19:07:50 localhost.localdomain kernel: NVRM: API mismatch: the client has the version 550.120, but NVRM: this kernel module has the version 550.107.02. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. ..... roll back to version 550.107.02 works -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175850] User mount option 'x-initrd.mount' vanishes during initrd transitions
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1175850 https://bugzilla.suse.com/show_bug.cgi?id=1175850#c29 --- Comment #29 from Stanislav Brabec <sbrabec(a)suse.com> --- Fabian Vogt, comment 27: ro mount for subvolumes is not supported with the recent API at all. So there is no backward incompatible change in fstab introduced by mountfd API. Just new possible mount options rbind,ro=recursive. With the recent API, it is interpreted as "rbind,ro". That behavior was introduced in util-linux-2.39. In the older versions, it was interpreted as "rbind" and "ro=recursive" passed to the kernel mount as a file system mount option. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231248] NetworkManager keeps updating resolv.conf
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231248 https://bugzilla.suse.com/show_bug.cgi?id=1231248#c2 --- Comment #2 from Daniel Pecka <nettezzaumanaa(a)gmail.com> --- Hi Stefan, thanks for your input ... maybe I've forgot to mention that it could be also considered as a regression because in past no such a timer that was periodically refreshing/enforcing policy was in NM .. I've run into this issue after recently upgrading from 15.1 (yep, please forgive me :D) at current 15.6 .. This is clearly new behaviour to see in journal stream of messages like this Oct 02 14:54:50 linux-1b6m NetworkManager[1878]: <info> [1727873690.9813] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 15:24:51 linux-1b6m NetworkManager[1878]: <info> [1727875491.0779] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 15:54:51 linux-1b6m NetworkManager[1878]: <info> [1727877291.2020] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 16:24:51 linux-1b6m NetworkManager[1878]: <info> [1727879091.5914] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 16:54:51 linux-1b6m NetworkManager[1878]: <info> [1727880891.4609] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 17:24:51 linux-1b6m NetworkManager[1878]: <info> [1727882691.7657] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 20:54:00 linux-1b6m NetworkManager[1878]: <info> [1727895240.4170] policy: set 'Pecka' (wlan0) as default for IPv4 routing and DNS Oct 02 20:54:04 linux-1b6m NetworkManager[1878]: <info> [1727895244.0664] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 20:54:52 linux-1b6m NetworkManager[1878]: <info> [1727895292.8249] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 21:24:52 linux-1b6m NetworkManager[1878]: <info> [1727897092.7127] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 21:54:52 linux-1b6m NetworkManager[1878]: <info> [1727898892.9391] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 22:24:53 linux-1b6m NetworkManager[1878]: <info> [1727900693.0543] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 22:54:53 linux-1b6m NetworkManager[1878]: <info> [1727902493.1649] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 23:24:53 linux-1b6m NetworkManager[1878]: <info> [1727904293.5259] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 02 23:54:53 linux-1b6m NetworkManager[1878]: <info> [1727906093.4778] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 03 00:24:53 linux-1b6m NetworkManager[1878]: <info> [1727907893.5797] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS Oct 03 08:34:49 linux-1b6m NetworkManager[1878]: <info> [1727937289.9427] policy: set 'Pecka' (wlan0) as default for IPv4 routing and DNS Oct 03 08:34:51 linux-1b6m NetworkManager[1878]: <info> [1727937291.4157] policy: set 'Pecka' (wlan0) as default for IPv6 routing and DNS or perhaps maybe it was there before but NM was not updating (or to be precise `restoring') /etc/resolv.conf every thirty minutes if the resolv.conf was governed by other application (like for instance standalone vpn client) .. regards, ~dan -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231236] Lastest audit package (audit-rules to be more specific) is not installable in containers
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231236 https://bugzilla.suse.com/show_bug.cgi?id=1231236#c1 Enzo Matsumiya <ematsumiya(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dcassany(a)suse.com | |) CC| |dcassany(a)suse.com --- Comment #1 from Enzo Matsumiya <ematsumiya(a)suse.com> --- @David thanks for the report. I've commited some changes to https://build.opensuse.org/package/show/home:ematsumiya:branches:security/a… I was able to confirm that 'zypper in -y audit' now installs without errors on a TW container. I'd appreciate if you could test it before I submit to factory. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231139] [SELinux] systemd-cryptsetup cannot read [/run/systemd | /var/lib/systemd]/pcrlock.json
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231139 https://bugzilla.suse.com/show_bug.cgi?id=1231139#c3 --- Comment #3 from Alberto Planas Dominguez <aplanas(a)suse.com> --- The full places are listed in https://www.freedesktop.org/software/systemd/man/latest/crypttab.html * tpm2-pcr-signature.json and tpm2-pcr-public-key.pem are searched for in /etc/systemd/, /run/systemd/, /usr/lib/systemd/ * pcrlock.json is searched for in /run/systemd/ and /var/lib/systemd/ Do you need more info? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231199] [systemd] Shutdown gets blocked with "A stop job is running for Cryptography Setup for cr_home" message
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231199 https://bugzilla.suse.com/show_bug.cgi?id=1231199#c3 --- Comment #3 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Franck Bui from comment #2) > So I suspect that the unit is stopped in your case probably due to the > modifications you did during your debug session. Uhm this is frustrating. I still have the original image with the issue, but I cannot reproduce it with new ones. -- You are receiving this mail because: You are on the CC list for the bug.

1 0