January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1235020] New: Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 Bug ID: 1235020 Summary: Hard freeze workqueue lockup mediatek bluetooth Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: andrea.ippo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, I've been experiencing random lockups on TW for a while now (more than a month): https://community.frame.work/t/workqueue-lockup-opensuse-tw/60430 (I'm the OP here) https://forums.opensuse.org/t/workqueue-lockup-should-i-file-a-bug/180387 I had to switch to Fedora for the past couple of weeks, and surprisingly I never experienced this issue there, which makes me think it might be related to the opensuse kernel (or maybe, just bad luck on TW). The problem seems to be related to bluetooth, as we can see by checking at the logs at the timestamp preceding the BUG - lockup entry by X seconds as specified in the error: Examples: https://pastebin.com/79dj1PeX https://pastebin.com/n3m1S8B7 In both cases if we go back by 58s we get around this part: Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Execution of wmt command timed out Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to send wmt patch dwnld (-110) Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to set up firmware (-110) Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110) Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: command 0xfd30 tx timeout Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: AOSP get vendor capabilities (-110) Jan 02 18:19:35 andromeda bluetoothd[1147]: Failed to set mode: Authentication Failed (0x05) When this happens, my entire DE becomes unresponsive, even systemctl reboot won't work and I'm forced to hard power off. I'm running 6.12.6-1-default Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c6 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ana.guerrero(a)suse.com Flags| |needinfo?(ana.guerrero@suse | |.com) --- Comment #6 from James Fehlig <jfehlig(a)suse.com> --- (In reply to Ana Guerrero from comment #5) > The bug still applies, we should make sure this doesn't happen in one year > again. As you can see from the referenced test code, libvirt has went to quite some extent to avoid the environment bug. IMO, the options are to remove the tests from the SUSE libvirt package, or reassign to the build service to investigate. Which do you prefer? > As mentioned in other comment, the issue consumed a significant amount of > time today. Why was time wasted? Why not simply inform the package maintainer about the build failure and be done with it? And how does a leaf package like libvirt block TW development? I guess I'm failing to understand why this issue was so critical that people unfamiliar with the package had to waste time investigating it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234781] Intel wifi ax200 issue with kernel 6.12.6
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234781 https://bugzilla.suse.com/show_bug.cgi?id=1234781#c9 --- Comment #9 from Frank Krüger <fkrueger(a)mailbox.org> --- ...or join https://bugzilla.kernel.org/show_bug.cgi?id=219597. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234781] Intel wifi ax200 issue with kernel 6.12.6
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234781 https://bugzilla.suse.com/show_bug.cgi?id=1234781#c8 --- Comment #8 from Frank Krüger <fkrueger(a)mailbox.org> --- This should be reported upstream, since the current patch comes from commit ccdc8fd86fc7b34630bc1ce2da26537219f8b473 Author: Emmanuel Grumbach <emmanuel.grumbach(a)intel.com> Date: Mon Dec 23 14:13:59 2024 +0200 wifi: iwlwifi: be less noisy if the NIC is dead in S3 commit 0572b7715ffd2cac20aac00333706f3094028180 upstream If the NIC is dead upon resume, try to catch the error earlier and exit earlier. We'll print less error messages and get to the same recovery path as before: reload the firmware. Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach(a)intel.com> Signed-off-by: Miri Korenblit <miriam.rachel.korenblit(a)intel.com> Link: https://patch.msgid.link/20241028135215.3a18682261e5.I18f336a4537378a4c1a85… Signed-off-by: Johannes Berg <johannes.berg(a)intel.com> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219597 Signed-off-by: Sasha Levin <sashal(a)kernel.org> You may use the wifi mailing list at https://marc.info/?l=linux-wireless or https://bugzilla.kernel.org. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234781] Intel wifi ax200 issue with kernel 6.12.6
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234781 https://bugzilla.suse.com/show_bug.cgi?id=1234781#c6 --- Comment #6 from Frank Krüger <fkrueger(a)mailbox.org> --- I am seeing these messages after wakeup from suspend as well, including kernel 6.13.0-rc5. So it's not specific to the current patch. Most importantly, it works without any loss of performance. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c5 Ana Guerrero <ana.guerrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Status|RESOLVED |REOPENED --- Comment #5 from Ana Guerrero <ana.guerrero(a)suse.com> --- (In reply to James Fehlig from comment #4) > I was about to revert your temporary fix in Virtualization/libvirt, but see > you've already done that. Thanks! > > I think we can close this bug now. Please reopen if you feel otherwise. > > Happy new year! :-) Hi James, The bug still applies, we should make sure this doesn't happen in one year again. As mentioned in other comment, the issue consumed a significant amount of time today. Happy new year! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c4 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #4 from James Fehlig <jfehlig(a)suse.com> --- I was about to revert your temporary fix in Virtualization/libvirt, but see you've already done that. Thanks! I think we can close this bug now. Please reopen if you feel otherwise. Happy new year! :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c3 --- Comment #3 from James Fehlig <jfehlig(a)suse.com> --- (In reply to Ana Guerrero from comment #1) > Created attachment 879378 [details] > libvirt virtimetest 2025 From that log the failing test is [ 176s] 28) Test localtime offset for "VIR11:00VID10:00,1/00:00:00,364/23:59:59" ... FAILED See the following code comment regarding failures of this test (and others) at the turn of the year https://gitlab.com/libvirt/libvirt/-/blob/master/tests/virtimetest.c?ref_ty… There's even an attempt to skip the tests when near the year end. See the isNearYearEnd() function earlier in the file. Apparently that didn't work in the OBS environment running this particular build. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234823] VitrtualBox-VMs refuse to stat after update to kernel 6.12.6-1-default (64-bit) because VirtualBox can't enable the AMD-V extension
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234823 https://bugzilla.suse.com/show_bug.cgi?id=1234823#c5 --- Comment #5 from Jan Engelhardt <jengelh(a)inai.de> --- Tumbleweed will have it with virtualbox-7.1.4-4.1.x86_64.rpm Download servers only have 7.1.4-3.1 currently -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234823] VitrtualBox-VMs refuse to stat after update to kernel 6.12.6-1-default (64-bit) because VirtualBox can't enable the AMD-V extension
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234823 https://bugzilla.suse.com/show_bug.cgi?id=1234823#c4 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Jan Engelhardt <jengelh(a)inai.de> --- was already submitted, but Factory publishing took a break across the change of calendar I think ---------------------------------------------------------------------------- r284 | anag+factory | 2024-12-30 11:50:51 | 92ac11091dc615d134c894b1d790b370 | 7.1.4 | rq1233843 - Set kvm.enable_virt_at_load=0 via a modprobe file -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234782] Kernel 6.12.6 with amdgpu breaks brightness control after resume
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234782 https://bugzilla.suse.com/show_bug.cgi?id=1234782#c9 --- Comment #9 from Frank Krüger <fkrueger(a)mailbox.org> --- (In reply to Jiri Slaby from comment #7) > Pushed the fix from: > https://lore.kernel.org/all/20241227073700.3102801-1-alexander.deucher@amd. > com/ Thank you! Version 6.12.8 works just fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1229281] New: [Package: teleport] Webassets outdated
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229281 Bug ID: 1229281 Summary: [Package: teleport] Webassets outdated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jankmann(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hope this is the right place to post this. The teleport package (https://build.opensuse.org/package/show/openSUSE:Factory/teleport) include outdated webassets which break the Web-GUI with version 16.X. The currently packaged Web-GUI still has the 15.X look and will not connect to any resource starting with 16.0.0. My current workaround is to replace the package binary with the official binary, which obviously breaks with each upgrade. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1234852] nct6775 (nct6798D) periodic delayed response and high CPU usage
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234852 https://bugzilla.suse.com/show_bug.cgi?id=1234852#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdelvare(a)suse.com, | |tiwai(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Adding Jean to Cc, who has a better clue about such a stuff. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234986] Kernel panic when system boot sometimes
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234986 https://bugzilla.suse.com/show_bug.cgi?id=1234986#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- A crash like this is usually an upstream problem, yes. Unfortunately we can't judge much because the most important pieces are already out of frame in your screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234766] dmesg btusb call trace jdy-67
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234766 https://bugzilla.suse.com/show_bug.cgi?id=1234766#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Leo.Bistmans@gmai | |l.com) CC| |tiwai(a)suse.com --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Is this a regression of the recent kernel? Or did the problem show up with the older kernels, too? The warning indicates some incorrect reference counter about tty port destruction, but it's hard to judge only from this. Please give the full dmesg output indicating this error. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234668] Kernel compilation with DRBD support fails with kernel-source-6.4.0-150600.23.30.1
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234668 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jack(a)suse.com, | |lduncan(a)suse.com, | |tiwai(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234623] DPC: RP PIO log size 0 is invalid (quirk needs to be added)
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234623 https://bugzilla.suse.com/show_bug.cgi?id=1234623#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- The upstream submission: https://lore.kernel.org/20250102164315.7562-1-tiwai@suse.de And I backported it to TW stable git branch now. It'll be included once after my PR gets merged and submitted to TW. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234623] DPC: RP PIO log size 0 is invalid (quirk needs to be added)
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234623 https://bugzilla.suse.com/show_bug.cgi?id=1234623#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Good to hear! I'm going to submit the patch to the upstream, then. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234774] rspamd 3.11.0 segfaults on Leap 15.6
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234774 https://bugzilla.suse.com/show_bug.cgi?id=1234774#c2 Marcus Rückert <mrueckert(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Marcus Rückert <mrueckert(a)suse.com> --- see the changes file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234053] Podman cannot create container in network
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234053 https://bugzilla.suse.com/show_bug.cgi?id=1234053#c10 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|CONFIRMED |RESOLVED --- Comment #10 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- I'll close this because there's not much we can do on our side since we don't control the WSL kernel, but you can still recompile it to fix the issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211761] vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1211761 https://bugzilla.suse.com/show_bug.cgi?id=1211761#c6 --- Comment #6 from Felix Miata <mrmazda(a)earthlink.net> --- (In reply to Paul Graff from comment #5) > I have a Nvidia Quadro K600 here but lack the skill to bisect. Would this > card help resolve the issue if it's in the right hands? K600 is Kepler, so possibly yes. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234993] Installation failed at partitioning
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234993 https://bugzilla.suse.com/show_bug.cgi?id=1234993#c6 --- Comment #6 from gilles renault <utilisateur.test(a)free.fr> --- Not better with an external HD. I can install windows 10 and Bazzite without problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233738] New: SELINUX prevents XRDP from working when in enforcing mode
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233738 Bug ID: 1233738 Summary: SELINUX prevents XRDP from working when in enforcing mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: jmscdba(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi Cathy, In my test TW system that is using selinux I found that xrdp is not working. When you attempt to RDP after entering your credentials a dialog is displayed which says the login is successful but then it says VNC error - problem connecting some problem Error conneting to user session If I run "setenforce 0" after booting then xrdp works fine. If I watch the journal when selinux is enforcing I find: xrdp-sesman[6092]: pam_unix(xrdp-sesman:session): session opened for user denise(uid=1001) by (uid=0) xrdp-sesman[6092]: pam_kwallet5(xrdp-sesman:session): pam_kwallet5: pam_sm_open_session xrdp-sesman[6149]: pam_kwallet5: final socket path: /run/user/1001/kwallet5.socket xrdp-sesman[6150]: pam_kwallet5: could not execute kwalletd from /usr/bin/kwalletd6 xrdp-sesman[6092]: pam_systemd(xrdp-sesman:session): New sd-bus connection (system-bus-pam-systemd-6092) opened. xrdp-sesman[6092]: pam_unix(xrdp-sesman:session): session closed for user denise xrdp-sesman[6092]: pam_kwallet5(xrdp-sesman:session): pam_kwallet5: pam_sm_close_session xrdp-sesman[6092]: pam_kwallet5(xrdp-sesman:setcred): pam_kwallet5: pam_sm_setcred systemd[1]: session-c7.scope: Deactivated successfully. ausearch shows these denied messages ausearch -ts boot | grep -i denied type=AVC msg=audit(1732232293.658:185): avc: denied { transition } for pid=2613 comm="xrdp-sesman" path="/usr/bin/kwalletd6" dev="sda2" ino=1779042 scontext=system_u:system_r:unconfined_service_t:s0 tcontext=unconfined_u:unconfined_r:unconfined_t:s0 tclass=process permissive=0 type=AVC msg=audit(1732232293.658:188): avc: denied { transition } for pid=2616 comm="xrdp-sesman" path="/usr/bin/bash" dev="sda2" ino=1719714 scontext=system_u:system_r:unconfined_service_t:s0 tcontext=unconfined_u:unconfined_r:unconfined_t:s0 tclass=process permissive=0 type=AVC msg=audit(1732232303.435:189): avc: denied { transition } for pid=2621 comm="xrdp-sesman" path="/usr/sbin/xrdp-chansrv" dev="sda2" ino=1455897 scontext=system_u:system_r:unconfined_service_t:s0 tcontext=unconfined_u:unconfined_r:unconfined_t:s0 tclass=process permissive=0 I'm still getting up to speed with selinux but it seems to me that xrdp tries to launch /usr/bin/xrdp-chansrv it is denied because there is no selinux policy to allow it, however, I thought when TARGETED mode was used then selinux would have allowed it ? Or does the package need to be updated to include a policy to allow xrdp so that it works in enforcing mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1234405] devel:microos/libeconf: Bug libeconf 0.7.5 causes systemd/sddm/pam/libc crash and prevents login
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234405 https://bugzilla.suse.com/show_bug.cgi?id=1234405#c15 --- Comment #15 from pallas wept <pallaswept(a)proton.me> --- (In reply to Stefan Schubert from comment #14) > Is this the right setting ? > https://github.com/openSUSE/libeconf/pull/229 Perhaps it is different between /usr/etc/environment.d and /etc/environment.d ? If that does not work in CI, I will test it here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c27 --- Comment #27 from Michal Kubeček <mkubecek(a)suse.com> --- OK, pushed into master now (with a cleanup of dependent options). Let's see how it goes. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232906] New: ppc64(le) isn't building the latest bpftrace due unresolvable lldb-devel
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1232906 Bug ID: 1232906 Summary: ppc64(le) isn't building the latest bpftrace due unresolvable lldb-devel Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Originally found in https://bugzilla.suse.com/show_bug.cgi?id=1224403#c8 https://build.opensuse.org/projects/devel:tools/packages/bpftrace/repositor… "unresolvable: nothing provides lldb-devel" -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c26 --- Comment #26 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi > e8cb5712703d Reapply "config: Disable CONFIG_FB_DEVICE (boo#1212947)" > (bsc#1232727) > 89074471a397 Revert "Reapply "config: Disable CONFIG_FB_DEVICE > (boo#1212947)" (bsc#1232727)" This inner cycle looks like a mistake and probably happened before the Plymouth bug reports came in. At least that's what I take from the commit messages. The fix for bsc#1232727 has been released in [1] ~3 weeks ago. That appears long enough to me to give some confidence in it. For the kernel config change I can prepare a test kernel and leave it out for another month or so. Let me also say that these interfaces are a constant source of bugs and security issues. [2] We have regular reports and no one seems to be able to get a hold on them. Dropping these interfaces is an improvement. [1] https://build.opensuse.org/request/show/1228732 [2] https://lore.kernel.org/linux-fbdev/674dac63.050a0220.ad585.0050.GAE@google… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228173] sssd: getsubids throws `libsubid_sss.so did not provide @subid_free@`
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228173 https://bugzilla.suse.com/show_bug.cgi?id=1228173#c6 Samuel Cabrero <scabrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(scabrero(a)suse.com | |) | --- Comment #6 from Samuel Cabrero <scabrero(a)suse.com> --- (In reply to Dylan Meysmans from comment #5) > (In reply to Samuel Cabrero from comment #4) > > (In reply to Dylan Meysmans from comment #3) > > > (In reply to Samuel Cabrero from comment #2) > > > > Fixed in sssd 2.10 beta2. > > > > > > When can we expect sssd 2.10 to arrive for Tumbleweed? I see it is already > > > in network:ldap. > > > > It will arrive soon, the OBS request is in place: > > https://build.opensuse.org/requests/1222104. Will need to wait for > > https://bugzilla.suse.com/show_bug.cgi?id=1230051, though. > > It seems that bug has been closed for some time now. Which other issues > prevent sssd 2.10 from arriving for Tumbleweed? Hi Dylan, we have to adjust the location of the permissions file for Tumbleweed (https://src.opensuse.org/jengelh/sssd/pulls/5) and the whitelist for the new permissions file needs to be updated after the 2.10.1 release (bsc#1233131). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carnold(a)suse.com Assignee|virt-bugs(a)suse.de |jfehlig(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222748] RIP: 0010:rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv] and RIP: 0033:0x7fac1690f3df - virtualbox host
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222748 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs(a)suse.de |jengelh(a)inai.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234782] New: Kernel 6.12.6 with amdgpu breaks brightness control after resume
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234782 Bug ID: 1234782 Summary: Kernel 6.12.6 with amdgpu breaks brightness control after resume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fkrueger(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Given TW20241220 with kernel 6.12.6 and resuming after suspend, the display brightness starts to increase until reaching its maximum value, and then switches off (Thinkpad T14 with AMD Ryzen 7 PRO 4750U). Since kernel version 6.12.4 works fine, I suspect that this was introduced with 6.12.5 and is due to commit 99a02eab82515343d536796aa917dee50aec1551 Author: Alex Deucher <alexander.deucher(a)amd.com> Date: Mon Nov 25 13:59:09 2024 -0500 drm/amdgpu: rework resume handling for display (v2) commit 73dae652dcac776296890da215ee7dec357a1032 upstream. Split resume into a 3rd step to handle displays when DCC is enabled on DCN 4.0.1. Move display after the buffer funcs have been re-enabled so that the GPU will do the move and properly set the DCC metadata for DCN. v2: fix fence irq resume ordering -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1180749] AMD Ryzen 4800H Renoir APU brightness control not working as found in some Lenovo Legion 5 15ARH05
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

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

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c25 --- Comment #25 from Michal Kubeček <mkubecek(a)suse.com> --- (In reply to Thomas Zimmermann from comment #23) > What are you talking about? This kernel option has been disabled exactly > once, which resulted in bsc#1232727. Apparently I mixed it with earlier FB related changes where we had similar apply/revert cycle pattern. But even for this option, this is actually third attempt to disable it: 7ce7d10b6941 config: Disable CONFIG_FB_DEVICE (boo#1212947) 86e3964b14ac Revert "config: Disable CONFIG_FB_DEVICE (boo#1212947)" (bsc#1232727) e8cb5712703d Reapply "config: Disable CONFIG_FB_DEVICE (boo#1212947)" (bsc#1232727) 89074471a397 Revert "Reapply "config: Disable CONFIG_FB_DEVICE (boo#1212947)" (bsc#1232727)" 6a2cbc6bdb98 config: Disable CONFIG_FB_DEVICE (boo#1212947) I don't think it should be so surprising that I have some doubts seeing the same claim (nobody needs this enabled any more) for the third time within few weeks after first two quickly turned out to be wrong. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228318] kernel crash on two laptops during shutdown/reboot
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228318 Eric Benton <erbenton(a)comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NORESPONSE |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228318] kernel crash on two laptops during shutdown/reboot
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228318 https://bugzilla.suse.com/show_bug.cgi?id=1228318#c8 Eric Benton <erbenton(a)comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(erbenton@comcast. | |net) | --- Comment #8 from Eric Benton <erbenton(a)comcast.net> --- I gave up and reformated and reinstalled and haven't had any issue since. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211761] vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1211761 https://bugzilla.suse.com/show_bug.cgi?id=1211761#c5 --- Comment #5 from Paul Graff <pj.opensuse(a)gmx.com> --- (In reply to Felix Miata from comment #4) > Upstream bug is not resolved, I added another GPU exhibiting problem (a > Kepler) only 2 weeks ago, and problem remains. I have a Nvidia Quadro K600 here but lack the skill to bisect. Would this card help resolve the issue if it's in the right hands? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c2 --- Comment #2 from Ana Guerrero <ana.guerrero(a)suse.com> --- After some hours, libvirt successfully started building again. This is good news, but the issue consumed a significant amount of time today. I've revoked the SR. As previously noted, the build was failing intermittently in a few different places. I've attached one of the build logs for review. Hopefully, we can identify the cause of this transient failure and prevent it from happening again. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c1 --- Comment #1 from Ana Guerrero <ana.guerrero(a)suse.com> --- Created attachment 879378 --> https://bugzilla.suse.com/attachment.cgi?id=879378&action=edit libvirt virtimetest 2025 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188954] black screen because dm tries to start before /dev/dri/card0 has been created during init
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1188954 https://bugzilla.suse.com/show_bug.cgi?id=1188954#c45 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mrmazda@earthlink | |.net) | --- Comment #45 from Felix Miata <mrmazda(a)earthlink.net> --- No wayland here, but it seems something may have changed that causes in most instances a retry in short order. Evidence from various hosts follows: gx280 (8086:2582): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 159.891] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 26 05:53:06 2024 /var/log/Xorg.0.log:[ 159.896] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log.old:[ 93.826] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 26 05:52:00 2024 /var/log/Xorg.0.log.old:[ 94.248] (II) xfree86: Adding drm device (/dev/dri/card0) gx28b (1002:94c3): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 249.858] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 20 00:44:59 2024 /var/log/Xorg.0.log:[ 249.866] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log:[ 249.878] (II) modeset(0): using drv /dev/dri/card0 /var/log/Xorg.0.log.old:[ 191.902] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 20 00:44:01 2024 /var/log/Xorg.0.log.old:[ 194.275] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log.old:[ 196.783] (II) modeset(0): using drv /dev/dri/card0 hp750 (8086:0042): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 114.930] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 18 19:51:14 2024 /var/log/Xorg.0.log:[ 114.932] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log:[ 114.976] (II) modeset(0): using drv /dev/dri/card0 /var/log/Xorg.0.log.old:[ 64.282] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 18 19:50:24 2024 /var/log/Xorg.0.log.old:[ 64.485] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log.old:[ 64.746] (II) modeset(0): using drv /dev/dri/card0 fi965 (1002:6611): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 104.776] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 10 22:21:40 2024 /var/log/Xorg.0.log:[ 106.164] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log:[ 106.993] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0 /var/log/Xorg.0.log:[ 107.557] (II) Applying OutputClass "AMDgpu" options to /dev/dri/card0 /var/log/Xorg.0.log.old:[ 101.818] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 10 22:12:29 2024 /var/log/Xorg.0.log.old:[ 102.608] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log.old:[ 103.528] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0 /var/log/Xorg.0.log.old:[ 104.091] (II) Applying OutputClass "AMDgpu" options to /dev/dri/card0 hpg33 (1002:9498): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 99.539] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 9 22:30:28 2024 /var/log/Xorg.0.log:[ 99.542] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log:[ 99.549] (II) Applying OutputClass "Radeon" to /dev/dri/card0 /var/log/Xorg.0.log.old:[ 57.664] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 9 22:29:46 2024 /var/log/Xorg.0.log.old:[ 59.566] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log.old:[ 60.246] (II) Applying OutputClass "Radeon" to /dev/dri/card0 big31 (1002:95c0): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 91.943] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 15 22:41:24 2024 /var/log/Xorg.0.log:[ 91.946] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log:[ 91.959] (II) modeset(0): using drv /dev/dri/card0 /var/log/Xorg.0.log.old:[ 50.571] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 15 22:40:44 2024 /var/log/Xorg.0.log.old:[ 51.429] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log.old:[ 51.855] (II) modeset(0): using drv /dev/dri/card0 gb970 (10de:0f00): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 39.550] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 5 08:18:41 2024 /var/log/Xorg.0.log:[ 39.552] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log:[ 39.560] (II) modeset(0): using drv /dev/dri/card0 /var/log/Xorg.0.log.old:[ 9.472] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 5 08:18:11 2024 /var/log/Xorg.0.log.old:[ 9.511] (EE) open /dev/dri/card0: No such file or directory /var/log/Xorg.0.log.old:[ 9.511] (EE) open /dev/dri/card0: No such file or directory /var/log/Xorg.0.log.old:[ 9.512] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. In other cases it seems I had to manually trigger a retry: ga88x (1002:130f): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 531.101] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 8 20:02:36 2024 /var/log/Xorg.0.log:[ 531.103] (II) xfree86: Adding drm device (/dev/dri/card1) /var/log/Xorg.0.log:[ 531.198] (II) modeset(0): using drv /dev/dri/card1 /var/log/Xorg.0.log:[ 531.199] (II) Applying OutputClass "AMDgpu" options to /dev/dri/card1 /var/log/Xorg.0.log.old:[ 18.979] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 8 19:54:04 2024 /var/log/Xorg.0.log.old:[ 19.019] (II) xfree86: Adding drm device (/dev/dri/card1) /var/log/Xorg.0.log.old:[ 19.165] (II) modeset(0): using drv /dev/dri/card1 /var/log/Xorg.0.log.old:[ 19.165] (II) Applying OutputClass "AMDgpu" options to /dev/dri/card1 p5bse (10de:0fc1): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 599.921] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 15 17:50:55 2024 /var/log/Xorg.0.log:[ 599.923] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log:[ 599.937] (II) modeset(0): using drv /dev/dri/card0 /var/log/Xorg.0.log.old:[ 58.967] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 15 17:41:54 2024 /var/log/Xorg.0.log.old:[ 59.410] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log.old:[ 59.917] (II) modeset(0): using drv /dev/dri/card0 mcp61 (10de:0402): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 728.494] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 18 21:40:32 2024 /var/log/Xorg.0.log:[ 728.496] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log:[ 728.510] (II) modeset(0): using drv /dev/dri/card0 /var/log/Xorg.0.log.old:[ 100.745] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 18 22:31:15 2024 /var/log/Xorg.0.log.old:[ 101.937] (II) xfree86: Adding drm device (/dev/dri/card0) /var/log/Xorg.0.log.old:[ 104.473] (II) modeset(0): using drv /dev/dri/card0 All hosts above are old PCs. The following is my newest (Rocket Lake): ab560 (8086:4c8b): # egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.* /var/log/Xorg.0.log:[ 61.294] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 31 01:22:24 2024 /var/log/Xorg.0.log:[ 61.295] (II) xfree86: Adding drm device (/dev/dri/card1) /var/log/Xorg.0.log:[ 61.353] (II) modeset(0): using drv /dev/dri/card1 /var/log/Xorg.0.log.old:[ 6.642] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 31 01:21:30 2024 /var/log/Xorg.0.log.old:[ 6.645] (II) xfree86: Adding drm device (/dev/dri/card1) /var/log/Xorg.0.log.old:[ 6.700] (II) modeset(0): using drv /dev/dri/card1 ab560 after the above instance doesn't seem any more have the issue, so it seems something may have changed after October to avoid the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233887] New: Have installer not set enforcing=1 in grub config, so /etc/selinux/config is ignored
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233887 Bug ID: 1233887 Summary: Have installer not set enforcing=1 in grub config, so /etc/selinux/config is ignored Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jsegitz(a)suse.com QA Contact: jsrain(a)suse.com CC: cathy.hu(a)suse.com, mmeisters(a)suse.com, security-team(a)suse.de Depends on: 1232496 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1232496 +++ sl micro 5.5 has enforcing=1 in grub config, so /etc/selinux/config is ignored should be removed, otherwise it is confusing for users why changing /etc/selinux/config does not do anything -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1234942] New: Maybe there are some incorrect configurations related to compiling Vim.
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234942 Bug ID: 1234942 Summary: Maybe there are some incorrect configurations related to compiling Vim. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: hxliang666(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 879361 --> https://bugzilla.suse.com/attachment.cgi?id=879361&action=edit Comparison of Results **My system information, wsl2:** NAME="openSUSE Tumbleweed" # VERSION="20241226" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20241226" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20241226:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20241226" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" **Problem description:** 1. After opening CPP files with gVim and exiting insert mode, the gVim cursor reacts with a delay when changing from the vertical bar to the block, even though I have removed many of my Vim configurations. 2. To address this, I manually compiled gVim and observed a different result: everything works correctly, and no delay occurs. **gVim provided by the system** VIM - Vi IMproved 9.1 (2024 Jan 02) Included patches: 1-908 Compiled by 'http://www.opensuse.org/' Huge version with GTK3 GUI. Features included (+) or not (-): +acl +file_in_path +mouse_urxvt -tag_any_white +arabic +find_in_path +mouse_xterm -tcl +autocmd +float +multi_byte +termguicolors +autochdir +folding +multi_lang +terminal -autoservername -footer -mzscheme +terminfo +balloon_eval +fork() +netbeans_intg +termresponse +balloon_eval_term +gettext +num64 +textobjects +browse -hangul_input +packages +textprop ++builtin_terms +iconv +path_extra +timers +byte_offset +insert_expand +perl +title +channel +ipv6 +persistent_undo +toolbar +cindent +job +popupwin +user_commands +clientserver +jumplist +postscript +vartabs +clipboard +keymap +printer +vertsplit +cmdline_compl +lambda +profile +vim9script +cmdline_hist +langmap -python +viminfo +cmdline_info +libcall +python3/dyn +virtualedit +comments +linebreak +quickfix +visual +conceal +lispindent +reltime +visualextra +cryptv +listcmds +rightleft +vreplace +cscope +localmap +ruby/dyn +wildignore +cursorbind +lua/dyn +scrollbind +wildmenu +cursorshape +menu +signs +windows +dialog_con_gui +mksession +smartindent +writebackup +diff +modify_fname -sodium +X11 +digraphs +mouse -sound +xattr +dnd +mouseshape +spell -xfontset -ebcdic +mouse_dec +startuptime +xim +emacs_tags +mouse_gpm +statusline -xpm +eval -mouse_jsbterm -sun_workshop +xsmp_interact +ex_extra +mouse_netterm +syntax +xterm_clipboard +extra_search +mouse_sgr +tag_binary -xterm_save -farsi -mouse_sysmouse -tag_old_static system vimrc file: "/etc/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" 3rd user vimrc file: "~/.config/vim/vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "/etc/gvimrc" user gvimrc file: "$HOME/.gvimrc" 2nd user gvimrc file: "~/.vim/gvimrc" 3rd user gvimrc file: "~/.config/vim/gvimrc" defaults file: "$VIMRUNTIME/defaults.vim" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/libxkbcommon -I/usr/include/wayland -I/usr/include/fribidi -I/usr/include/libpng16 -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/gio-unix-2.0 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -O2 -Wall -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -g -Wall -pipe -fno-strict-aliasing -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -flto=auto -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXt -lX11 -lSM -lICE -lm -lselinux -ltinfo -lrt -lacl -lgpm -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -L/usr/local/lib64 -fstack-protector-strong -L/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -lperl -lm -ldl -lcrypt -lpthread **gVim Compiled by me** VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Dec 31 2024 08:58:55) Included patches: 1-981 Compiled by banana@Banana Huge version with GTK3 GUI. Features included (+) or not (-): +acl +file_in_path +mouse_urxvt -tag_any_white +arabic +find_in_path +mouse_xterm -tcl +autocmd +float +multi_byte +termguicolors +autochdir +folding +multi_lang +terminal -autoservername -footer -mzscheme +terminfo +balloon_eval +fork() +netbeans_intg +termresponse +balloon_eval_term +gettext +num64 +textobjects +browse -hangul_input +packages +textprop ++builtin_terms +iconv +path_extra +timers +byte_offset +insert_expand +perl +title +channel +ipv6 +persistent_undo +toolbar +cindent +job +popupwin +user_commands +clientserver +jumplist +postscript +vartabs +clipboard +keymap +printer +vertsplit +cmdline_compl +lambda +profile +vim9script +cmdline_hist +langmap -python +viminfo +cmdline_info +libcall +python3 +virtualedit +comments +linebreak +quickfix +visual +conceal +lispindent +reltime +visualextra +cryptv +listcmds +rightleft +vreplace +cscope +localmap +ruby +wildignore +cursorbind +lua +scrollbind +wildmenu +cursorshape +menu +signs +windows +dialog_con_gui +mksession +smartindent +writebackup +diff +modify_fname -sodium +X11 +digraphs +mouse -sound +xattr +dnd +mouseshape +spell -xfontset -ebcdic +mouse_dec +startuptime +xim +emacs_tags -mouse_gpm +statusline -xpm +eval -mouse_jsbterm -sun_workshop -xsmp +ex_extra +mouse_netterm +syntax +xterm_clipboard +extra_search +mouse_sgr +tag_binary -xterm_save -farsi -mouse_sysmouse -tag_old_static system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" 3rd user vimrc file: "~/.config/vim/vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "$VIM/gvimrc" user gvimrc file: "$HOME/.gvimrc" 2nd user gvimrc file: "~/.vim/gvimrc" 3rd user gvimrc file: "~/.config/vim/gvimrc" defaults file: "$VIMRUNTIME/defaults.vim" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/local/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/libxkbcommon -I/usr/include/wayland -I/usr/include/fribidi -I/usr/include/libpng16 -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/gio-unix-2.0 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DWITH_GZFILEOP -I/usr/include/libmount -I/usr/include/blkid -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -Wl,--as-needed -o vim -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lXt -lX11 -lSM -lICE -lm -ltinfo -lselinux -L/usr/lib -llua5.4 -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -L/usr/local/lib64 -fstack-protector-strong -L/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -lperl -lm -ldl -lcrypt -lpthread -L/usr/lib64/python3.11/config-3.11-x86_64-linux-gnu -lpython3.11 -ldl -lm -lruby3.3 -lm -lpthread -L/usr/lib64 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c24 --- Comment #24 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi (In reply to Jiri Slaby from comment #21) > (In reply to Michal Kubeček from comment #20) > > Are you really sure that this time it is for real and we are not going to > > repeat the same dance again? Couldn't we at least wait until after 6.13 > > final to have a bit more time for testing before it hits Tumbleweed and > > its users? > > And perhaps ask users to test TW with Kernel:HEAD once it contains this > change. I can do that, but I feel like it wouldn't make much of a difference. As this change has been discussed on factory; only those participants would likely test anyway. > > Note I won't take this config change with the big master->stable merge. The > merge usually has enough its own bugs to solve. That's OK. I can prepare a separate change for stable. > > So either I take this into stable either before 5.13 merge (i.e. cherry-pick > it) or after (a revert during the big merge and > cherry-pick/revert-the-revert later) ;). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c23 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tzimmermann@suse. | |com) | --- Comment #23 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi (In reply to Michal Kubeček from comment #20) > This has been going on for months and it is getting more and more > ridiculous. Please keep it professional. > The option has been disabled multiple times, each time with the > same reasoning ("nobody needs this any more") and each time with the same > result: getting reenabled within a week or two because it turns out it does > actually break something. What are you talking about? This kernel option has been disabled exactly once, which resulted in bsc#1232727. We reverted the kernel change to get the fix done. But bsc#1232727 has been trivial to resolve. The whole fallout that happened afterwards entirely goes back to the dire state that our Plymouth package is in. It is unrelated to the kernel's fbdev interface. > > Are you really sure that this time it is for real and we are not going to > repeat the same dance again? Couldn't we at least wait until after 6.13 > final to have a bit more time for testing before it hits Tumbleweed and > its users? I sent out a message to the factory list to collect possible use cases in Oct 2023. And then again a reminder in Oct 2024. [1] The two actionable use cases I heard about were fbiterm and the links web browser in 'graphics mode' (mentioned by a single person). We've removed the fbiterm in boo#1224053 in May 2024. The maintainer of links has been working on converting the program to DRM interface AFAIK. Meanwhile links continues to work in pure text mode. [1] https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223838] Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau)
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1223838 https://bugzilla.suse.com/show_bug.cgi?id=1223838#c64 --- Comment #64 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Jiri Slaby from comment #63) > (In reply to Takashi Iwai from comment #19) > > The upstream submission: > > https://lore.kernel.org/all/20240517110853.8481-1-tiwai@suse.de/ > > It somehow fell through the cracks. Care to ping them/resend? Done: https://lore.kernel.org/all/20250102114944.11499-1-tiwai@suse.de/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234871] systemdboot_widgets shows undefined method >= for nil
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234871 https://bugzilla.suse.com/show_bug.cgi?id=1234871#c2 --- Comment #2 from Stefan Schubert <schubi(a)suse.com> --- >When converting my system from Legacy to sdboot /boot/efi is empty Hm, empty efi directory is strange. Have have you converted your system ? Is it an EFI system ? >I installed yast2-bootloader as https://microos.opensuse.org/blog/2023-12-20-sdboot-fde/ says yast2 has sdboot support It says: "Soon after the announcement, yast-bootloader gained support for it for new installations." So, the important word is "new installation" and not "migration" :-) Anyway, currently I cannot reproduce the error but perhaps we find a solution for it ..... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c22 --- Comment #22 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #21) > (In reply to Michal Kubeček from comment #20) > > Are you really sure that this time it is for real and we are not going to > > repeat the same dance again? Couldn't we at least wait until after 6.13 > > final to have a bit more time for testing before it hits Tumbleweed and > > its users? > > And perhaps ask users to test TW with Kernel:HEAD once it contains this > change. Or even build Kernel:stable + config.addon in your home and let users test that at first (I would once you post a link to the factory list). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234692] Moval of dbus-launch to dbus-daemon prevents start of Dolphin super user mode
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234692 https://bugzilla.suse.com/show_bug.cgi?id=1234692#c6 --- Comment #6 from Christophe Marin <christophe(a)krop.fr> --- (In reply to John Smith from comment #4) > The below update broke Dolphin's right click context menu functionality. > > https://build.opensuse.org/request/show/1231914 > > Right click> Open Folder With> File Manager - Super User Mode. > Fixed with https://build.opensuse.org/request/show/1233825 it just needs a new snapshot to be released. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c21 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #21 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Michal Kubeček from comment #20) > Are you really sure that this time it is for real and we are not going to > repeat the same dance again? Couldn't we at least wait until after 6.13 > final to have a bit more time for testing before it hits Tumbleweed and > its users? And perhaps ask users to test TW with Kernel:HEAD once it contains this change. Note I won't take this config change with the big master->stable merge. The merge usually has enough its own bugs to solve. So either I take this into stable either before 5.13 merge (i.e. cherry-pick it) or after (a revert during the big merge and cherry-pick/revert-the-revert later) ;). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222902] Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222902 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mrmazda(a)earthlink.net | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234500] New: VUL-0: : singularity-ce: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234500 Bug ID: 1234500 Summary: VUL-0: : singularity-ce: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/432234/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: eich(a)suse.com Reporter: gianluca.gabrielli(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1234482 Target Milestone: --- Found By: --- Blocker: --- Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/cry...@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 https://github.com/golang/crypto/commit/b4f1988a35dee11ec3e05d6bf3e90b695fb… https://go.dev/cl/635315 https://go.dev/issue/70779 https://groups.google.com/g/golang-announce/c/-nPEi39gI4Q/m/cGVPJCqdAQAJ https://pkg.go.dev/vuln/GO-2024-3321 http://www.openwall.com/lists/oss-security/2024/12/11/2 https://bugzilla.redhat.com/show_bug.cgi?id=2331720 https://github.com/CVEProject/cvelistV5/blob/main//cves/2024/45xxx/CVE-2024… -- You are receiving this mail because: You are on the CC list for the bug.

1 4