January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[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