December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1154445] NM-configured bridge takes long time to negotiate IP address on system resume
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1154445 https://bugzilla.suse.com/show_bug.cgi?id=1154445#c3 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #3 from Jonathan Kang <songchuan.kang(a)suse.com> --- (In reply to Jonathan Kang from comment #2) > I'm not clear what caused such a difference atm. This setting(bridge.forward-delay) in the bridge connection affects the time spent in LISTENING and LEARNING state. You can run the follwing command to reduce it to minimum value allowed. > nmcli connection modify your-bridge-connection-name bridge.forward-delay 2 For more information, check out https://www.networkmanager.dev/docs/api/latest/settings-bridge.html. I'm closing this bug as RESOLVED INVALID, as this is more of a setting issue than a bug. Thanks for report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233542] New: patterns-base forces chrony which prevents use of other ntpd applications.
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233542 Bug ID: 1233542 Summary: patterns-base forces chrony which prevents use of other ntpd applications. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am using ntpd-rs which correctly conflicts on other ntp-daemons: https://build.opensuse.org/projects/network:time/packages/ntpd-rs/files/ntp… This causes leap upgrades to break, since patterns-base-base-20200505-59 now *requires* chrony. Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Problem: 1: the to be installed patterns-base-base-20200505-59.1.x86_64 requires 'chrony', but this requirement cannot be provided not installable providers: chrony-4.6-165.5.i586[network_time] chrony-4.6-165.5.x86_64[network_time] chrony-4.6-1.2.x86_64[openSUSE-20240830-0] chrony-4.6-1.2.x86_64[repo-oss] Solution 1: deinstallation of ntpd-rs-1.3.0-13.4.x86_64 Solution 2: deinstallation of patterns-base-base-20200505-57.1.x86_64 Solution 3: keep obsolete patterns-base-base-20200505-57.1.x86_64 Solution 4: break patterns-base-base-20200505-59.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): patterns-base-base should *not force* chrony on systems which prevents upgrades. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232759] Using bbswitch On Optimus laptop to disable NVIDIA card is problematic with newer kernels
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232759 https://bugzilla.suse.com/show_bug.cgi?id=1232759#c2 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. Recently I learned that one should no longer rely on tools like suse-prime, bbswitch, bumblebee, etc. These just do more harm than have benefit! Things work out-of-the box with current systems. Please check this out. https://negativo17.org/prime-optimus-laptops-and-multi-gpu-systems/ I won't drop suse-prime/bbswitch immediately but will no longer install and configure it together with G06 driver packages beginning early next year. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234055] Unable to reach dual monitor resolution with 2x 4k UHD side by side to 7680x2160
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c10 Otrebor Igorig <otrebor(a)hispeed.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(otrebor(a)hispeed.c | |h) | --- Comment #10 from Otrebor Igorig <otrebor(a)hispeed.ch> --- Thanks for the swift reply. I installed kernel-default version 6.12.1-lp155.14.1.g3c4672e and can report the following: - the full resolution works - success However the kernel has a few other glitches (which weren't there before): - Initialization of the external monitors not performed until actually logging in - intermittent lags when starting the X11 desktop - more lags when using the desktop - KDE Desktop has a few problems with the new setup - Sound device selection does show but not play sound over bluetooth - flickering video example: https://meteonews.tv/Wetter/Schweiz/de watch the moderator when they move. interestingly youtube videos work without flickering. to summarize - the new full resolution works - thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219943] Certificate error while fetching from https://debuginfod.opensuse.org
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1219943 Martin Liška <martin.liska(a)hey.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|martin.liska(a)hey.com |screening-team-bugs(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234114] New: udev: Contains symlinks /run/udev/links/by-partlabel/primary/
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234114 Bug ID: 1234114 Summary: udev: Contains symlinks /run/udev/links/by-partlabel/primary/ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4680054/modules/udev _no_symlink/steps/388 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: avinesh.kumar(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-udev-no-partlabel-links@64bit fails in [udev_no_symlink](https://openqa.opensuse.org/tests/4680054/modules/udev_no_… In tumbleweed, original test (https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/test…) fails at assert_script_run('journalctl -u detect-part-label-duplicates.service --no-pager | grep "Warning: a high number of partitions uses"'); as there is no such systemd service present in tw which will log this warning message. (https://openqa.opensuse.org/tests/4672363#step/udev_no_symlink/388) On removing this check from the test, I see that symlinks being created issue is present - https://openqa.opensuse.org/tests/4673222#step/udev_no_symlink/390 --- # test $(grep -r "E:ID_PART_ENTRY_NAME=openqapart" /run/udev/data | wc -l) -eq 10; echo AJmKE-$?- AJmKE-0- # ls -laR /run/udev/links/*by-partlabel*{primary,logical}/*; echo 13BTV-$?- ls: cannot access '/run/udev/links/*by-partlabel*logical/*': No such file or directory lrwxrwxrwx 1 root root 11 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:17 -> 0:/dev/vdb1 lrwxrwxrwx 1 root root 11 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:18 -> 0:/dev/vdb2 lrwxrwxrwx 1 root root 11 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:19 -> 0:/dev/vdb3 lrwxrwxrwx 1 root root 11 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:20 -> 0:/dev/vdb4 lrwxrwxrwx 1 root root 11 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:21 -> 0:/dev/vdb5 lrwxrwxrwx 1 root root 11 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:22 -> 0:/dev/vdb6 lrwxrwxrwx 1 root root 11 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:23 -> 0:/dev/vdb7 lrwxrwxrwx 1 root root 11 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:24 -> 0:/dev/vdb8 lrwxrwxrwx 1 root root 11 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:25 -> 0:/dev/vdb9 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:26 -> 0:/dev/vdb10 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:27 -> 0:/dev/vdb11 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:28 -> 0:/dev/vdb12 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:29 -> 0:/dev/vdb13 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:30 -> 0:/dev/vdb14 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b254:31 -> 0:/dev/vdb15 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b259:0 -> 0:/dev/vdb16 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b259:1 -> 0:/dev/vdb17 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b259:10 -> 0:/dev/vdb26 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b259:11 -> 0:/dev/vdb27 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b259:12 -> 0:/dev/vdb28 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b259:13 -> 0:/dev/vdb29 lrwxrwxrwx 1 root root 12 Nov 28 09:38 /run/udev/links/disk\x2fby-partlabel\x2fprimary/b259:14 -> 0:/dev/vdb30 ___ Last good: unknown for Tumbleweed ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… Bug for this issue on SLE15-SP6: https://bugzilla.suse.com/show_bug.cgi?id=1217878 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1234113] New: system stopped booting with encrypted disk
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234113 Bug ID: 1234113 Summary: system stopped booting with encrypted disk Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lukaswu(a)go2.pl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, I'm using current openSUSE Tumbleweed and with latest updates my system stopped booting properly- all my partitions are enecrypted, I provide pass for /boot, it works fine- grub is able to start booting process of the kernel, then it asks for the pass for root partition- despite providing correct pass, after the third attempt the progress cycle is rotating but nothing else happens. I booted my laptop from the USB, I was able to check root partition both crypt and filesystem, no error found, to be 10!% sure, it is not a problem of any special character that became forbidden I changed the pass, yet it will not boot. I tried others kernel too, what I have are: kernel-longterm-6.6.63-1.1.x86_64 kernel-longterm-6.6.62-1.1.x86_64 kernel-default-6.11.7-1.1.x86_64 kernel-default-6.11.8-1.1.x86_64 all of them are failing, as of now only 6.6.62-1-longterm in recovery mode worked for me. Please advise how to diagnose this issue deeper. lukas -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234112] New: Current MESA version causes GPU artifacts on AMD GPUs
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234112 Bug ID: 1234112 Summary: Current MESA version causes GPU artifacts on AMD GPUs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mcdonald.w(a)icloud.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently available mesa version on Tumeblweed causes gpu artifacts when alt-tabbing from full-screen games and on my system in particular, has caused Gnome or Wayland (or both) to exit to greeter on more than one occasion. It's my understanding this bug has been reverted on git but has not been made available in a point release yet to address it. It would be a simple matter for OpenSUSE to backport this fix Bisect here: https://gitlab.freedesktop.org/mesa/mesa/-/commit/c49a71c03c9166b0814db9242… More info: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11996 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234053] New: Podman cannot create container in network
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234053 Bug ID: 1234053 Summary: Podman cannot create container in network Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: rbobro(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Minimal example: ``` radek@DESKTOP-J12T7SE ~/src> podman network ls NETWORK ID NAME DRIVER 2f259bab93aa podman bridge radek@DESKTOP-J12T7SE ~/src> podman network create testnet testnet radek@DESKTOP-J12T7SE ~/src> podman run -itd --network=testnet busybox Resolved "busybox" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf) Trying to pull docker.io/library/busybox:latest... Getting image source signatures Copying blob 430378704d12 done | Copying config 517b897a6a done | Writing manifest to image destination internal:0:0-0: Error: Could not process rule: No such file or directory internal:0:0-0: Error: Could not process rule: No such file or directory Error: netavark: nftables error: nft did not return successfully while applying ruleset ``` This started happening after a `zypper dup` over the weekend. Now, I must admit it's been a few months since I have updated this install, so I'm not sure exactly when the regression happened. We use openSUSE Tumbleweed on Windows in WSL to test out container workloads locally and this has started happening to all developers who have updated their installs. I'm not sure if this is WSL specific or not, as I don't have access to a native install of Tumbleweed, but it is happening even in brand new installs of Tumbleweed in WSL. I've tried to figure out exactly what's going on, but I'm drawing a blank. Let me know if there are any other details I can provide to help figure this out. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1234110] VUL-0: matrix-synapse: multiple security issues in matrix-synapse
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234110 Camila Camargo de Matos <camila.matos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://smash.suse.de/issue | |/430994/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0