[Bug 1234301] New: Login screen does not display after update to 20241105

https://bugzilla.suse.com/show_bug.cgi?id=1234301 Bug ID: 1234301 Summary: Login screen does not display after update to 20241105 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: alanhants@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 879010 --> https://bugzilla.suse.com/attachment.cgi?id=879010&action=edit Xorg log from Tumbleweed 20241104 (last working version) Following an update to Tumbleweed 20241105, the login screen (SDDM) no longer displays, instead the screen simply turns blank with no mouse pointer. Rolling back to the previous release clears the problem. I suspect that this is an XOrg problem, and have attached two Xorg log files: one from 20241104 (working XOrg) and 20241105 (broken XOrg). -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 https://bugzilla.suse.com/show_bug.cgi?id=1234301#c1 --- Comment #1 from Alan Hughes <alanhants@gmail.com> --- Created attachment 879011 --> https://bugzilla.suse.com/attachment.cgi?id=879011&action=edit Xorg log from Tumbleweed 20241105 (broken version) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 Alan Hughes <alanhants@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE Workspace (Plasma) |X.Org QA Contact|qa-bugs@suse.de |gfx-bugs@suse.de Assignee|opensuse-kde-bugs@opensuse. |gfx-bugs@suse.de |org | -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 https://bugzilla.suse.com/show_bug.cgi?id=1234301#c2 --- Comment #2 from Alan Hughes <alanhants@gmail.com> --- This is definitely an XOrg problem; I managed to update to 20241106 but only after I had locked the XOrg server packages so that they would not be replaced during the update process. KDE Plasma is not a problem. Allowing the XOrg packages to subsequently update reproduced the issue. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 https://bugzilla.suse.com/show_bug.cgi?id=1234301#c3 --- Comment #3 from Fabian Vogt <fabian@ritter-vogt.de> --- *** Bug 1234297 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 https://bugzilla.suse.com/show_bug.cgi?id=1234301#c4 Fabian Vogt <fabian@ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de --- Comment #4 from Fabian Vogt <fabian@ritter-vogt.de> --- Maybe a regression in 20241206's update to Mesa 24.3.1? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 https://bugzilla.suse.com/show_bug.cgi?id=1234301#c10 --- Comment #10 from Alan Hughes <alanhants@gmail.com> --- The original report had incorrect TW release numbers: 20241104 should be 20241204 20241105 should be 20241205 Basically my system is up to date, but my brain is currently in a different space-time dimension to shifted my one month back. My bad, my sincere apologies for the confusion this has caused. My laptop is currently running 20241206 except I locked the X server packages to the version in 20241204 in order to get a usable system. Updating the X server packages results in the error symptoms noted in the original report. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 https://bugzilla.suse.com/show_bug.cgi?id=1234301#c12 --- Comment #12 from Alan Hughes <alanhants@gmail.com> --- (In reply to Stefan Dirsch from comment #11)
Ok. We had a TW 20241204 release but no TW 20241205 release. At least I couldn't find an announcement for it on the opensuse-factory ML.
And we had a 20241206 release.
Date: Sat, 07 Dec 2024 16:00:44 +0000 From: Dominique Leuenberger <dimstar@suse.de> To: factory@lists.opensuse.org Subject: New Tumbleweed snapshot 20241206 released!
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/ overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20241206
Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports
Packages changed: Mesa (24.3.0 -> 24.3.1) Mesa-drivers (24.3.0 -> 24.3.1) cdparanoia gawk libdrm (2.4.123 -> 2.4.124) libplist libsoup mc psmisc python-MarkupSafe python-rich python311 (3.11.10 -> 3.11.11) python311-core (3.11.10 -> 3.11.11) virt-manager
=== Details ===
==== Mesa ==== Version update (24.3.0 -> 24.3.1) Subpackages: Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 libgbm1
- Update to release 24.3.1 - -> https://docs.mesa3d.org/relnotes/24.3.1
==== Mesa-drivers ==== Version update (24.3.0 -> 24.3.1) Subpackages: Mesa-dri Mesa-gallium Mesa-libva libxatracker2
- Update to release 24.3.1 - -> https://docs.mesa3d.org/relnotes/24.3.1 [...] ==== libdrm ==== Version update (2.4.123 -> 2.4.124) Subpackages: libdrm2 libdrm_amdgpu1 libdrm_intel1 libdrm_nouveau2 libdrm_radeon1
- update to 2.4.124 * include/drm/README: update drm-next link to use gitlab instead of cgit * modetest: simplify planar YUV handling * modetest: add support for YUV422 and YUV444 plane format * xf86drm: print AMD modifiers properly * tests/util: Call `drmGetDevices2()` instead of `drmOpen()`ing all modules * android: add genrule for generated_static_table_fourcc.h * modetest: Make modetest availble to vendor on Android * build: simplify Linux system check [...]
Mesa, libdrm (+ subpackages) are the best candidates here. So which packages exaclty did you block?
Sorry to contradict you, but there *was* a 20241205 release of TW; the change notes for it can be found at https://download.opensuse.org/tumbleweed/iso/Changes.20241205.txt. I will include these changes as an additional attachment. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 Alan Hughes <alanhants@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Login screen does not |Login screen does not |display after update to |display after update to |20241206 |20241205 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 https://bugzilla.suse.com/show_bug.cgi?id=1234301#c15 --- Comment #15 from Alan Hughes <alanhants@gmail.com> --- (In reply to Stefan Dirsch from comment #14)
Ok. The announcement for that is missing on the mailing list. I'm subscribed.
==== xorg-x11-server ==== Subpackages: xorg-x11-server-Xvfb xorg-x11-server-extra
- no longer apply and remove u_xfree86-activate-GPU-screens-on-autobind.patch since it's no longer needed and might be harmful even ... (tested successfully on Thinkpad P16 with Intel/NVIDIA hybrid graphics) - remove no longer applied and no longer needed patch n_xserver-optimus-autoconfig-hack.patch (feature implemented upstream)
Ok. So you blocked the update of xorg-x11-server package to avoid the issue?
Correct; that package is currently locked until this problem is resolved. All other packages from 20241205 and 20241206 have been successfully installed. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1234301 https://bugzilla.suse.com/show_bug.cgi?id=1234301#c22 --- Comment #22 from Alan Hughes <alanhants@gmail.com> --- Confirmed that the fix works. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com