As per title. Any input instantly crashes the login page into a black screen. I can interact with it just fine with the mouse, though not even the virtual keyboard works (it just doesn’t input anything into the boxes).
Ctrl+Alt+BSP (twice) resets it just fine.
AMD Radeon 7800XT, last session open was a Wayland session, but I’m not sure if that is relevant.
Update: I managed to login… by using the virtual keyboard on my second monitor (??). For some reason it accepted input (though the main monitor did not).
Still, this does not fix the actual problem.
Anyone? I want to clarify that this still almost completely stops me from logging in and using my PC. I’m honestly avoiding logging out or restarting it just in case the virtual keyboard method stops working for some reason.
May 03 18:26:00 localhost.localdomain kernel: sddm-greeter-qt[10827]: segfault at 3fffffffff9 ip 00007f63beeaae85 sp 00007ffe9a6f5b80 error 4 in libc.so.6[aae85,7f63bee28000+174000] likely on CPU 1 (core 1, socket 0)
May 03 18:26:00 localhost.localdomain kernel: Code: 90 90 90 f3 0f 1e fa 90 90 48 85 ff 0f 84 53 01 00 00 41 57 41 56 41 55 41 54 55 48 8d 6f f0 48 83 ec 20 4c 8b 25 53 af 14 00 <48> 8b 47 f8 64 45 8b 2c 24 a8 02 0f 85 d>
May 03 18:26:00 localhost.localdomain systemd-coredump[10899]: Process 10827 (sddm-greeter-qt) of user 463 terminated abnormally with signal 11/SEGV, processing...
May 03 18:26:00 localhost.localdomain systemd[1]: Started Process Core Dump (PID 10899/UID 0).
May 03 18:26:00 localhost.localdomain systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
May 03 18:26:01 localhost.localdomain systemd-coredump[10900]: [🡕] Process 10827 (sddm-greeter-qt) of user 463 dumped core.
Stack trace of thread 10827:
#0 0x00007f63beeaae85 free (libc.so.6 + 0xaae85)
#1 0x00007f63bf4d4478 xkb_keymap_unref (libxkbcommon.so.0 + 0x1e478)
#2 0x00007f63bf4d598c xkb_state_unref (libxkbcommon.so.0 + 0x1f98c)
#3 0x00007f63bb137687 n/a (libQt6XcbQpa.so.6 + 0x6d687)
#4 0x00007f63bb112f9d _ZN14QXcbConnection14handleXcbEventEP19xcb_generic_event_t (libQt6XcbQpa.so.6 + 0x48f9d)
#5 0x00007f63bb11968c _ZN14QXcbConnection16processXcbEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6XcbQpa.so.6 + 0x4f68c)
#6 0x00007f63bb132607 n/a (libQt6XcbQpa.so.6 + 0x68607)
#7 0x00007f63bed09678 n/a (libglib-2.0.so.0 + 0x5f678)
#8 0x00007f63bed0b3d8 n/a (libglib-2.0.so.0 + 0x613d8)
#9 0x00007f63bed0bbec g_main_context_iteration (libglib-2.0.so.0 + 0x61bec)
#10 0x00007f63bfa1a013 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x41a013)
#11 0x00007f63bf7c24db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1c24db)
#12 0x00007f63bf7baddc _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x1baddc)
#13 0x00005561e593afb1 n/a (/usr/bin/sddm-greeter-qt6 + 0x15fb1)
#14 0x00007f63bee2b12e __libc_start_call_main (libc.so.6 + 0x2b12e)
#15 0x00007f63bee2b1f9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2b1f9)
#16 0x00005561e59404a5 n/a (/usr/bin/sddm-greeter-qt6 + 0x1b4a5)
Stack trace of thread 10833:
#0 0x00007f63beea1c32 __syscall_cancel_arch (libc.so.6 + 0xa1c32)
#1 0x00007f63bee9581c __internal_syscall_cancel (libc.so.6 + 0x9581c)
#2 0x00007f63bee95fec __futex_abstimed_wait_common (libc.so.6 + 0x95fec)
#3 0x00007f63bee98a78 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x98a78)
#4 0x00007f63b1b8cc39 n/a (libgallium-25.0.4.so + 0x58cc39)
#5 0x00007f63b1b5885b n/a (libgallium-25.0.4.so + 0x55885b)
#6 0x00007f63b1b8cb77 n/a (libgallium-25.0.4.so + 0x58cb77)
#7 0x00007f63bee99546 start_thread (libc.so.6 + 0x99546)
#8 0x00007f63bef1d94c __clone3 (libc.so.6 + 0x11d94c)
Stack trace of thread 10828:
#0 0x00007f63beea1c32 __syscall_cancel_arch (libc.so.6 + 0xa1c32)
#1 0x00007f63bee9581c __internal_syscall_cancel (libc.so.6 + 0x9581c)
#2 0x00007f63bee95871 __syscall_cancel (libc.so.6 + 0x95871)
#3 0x00007f63bef0f87a __poll (libc.so.6 + 0x10f87a)
#4 0x00007f63c11e2a62 n/a (libxcb.so.1 + 0xea62)
#5 0x00007f63c11e44bc xcb_wait_for_event (libxcb.so.1 + 0x104bc)
#6 0x00007f63bb12f938 n/a (libQt6XcbQpa.so.6 + 0x65938)
#7 0x00007f63bf92c22a n/a (libQt6Core.so.6 + 0x32c22a)
#8 0x00007f63bee99546 start_thread (libc.so.6 + 0x99546)
#9 0x00007f63bef1d94c __clone3 (libc.so.6 + 0x11d94c)
If i remember right, there was a thread which mentioned that this was XCB related.
Edit: This one…
But after reading again…it seems not really related to your issue.
Sorry, there’s more to the stacktrace. There’s a bunch of these:
Stack trace of thread 10872:
#0 0x00007f63beea1c32 __syscall_cancel_arch (libc.so.6 + 0xa1c32)
#1 0x00007f63bee9581c __internal_syscall_cancel (libc.so.6 + 0x9581c)
#2 0x00007f63bee95fec __futex_abstimed_wait_common (libc.so.6 + 0x95fec)
#3 0x00007f63bee98a78 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x98a78)
#4 0x00007f63b1b8cc39 n/a (libgallium-25.0.4.so + 0x58cc39)
#5 0x00007f63b1b5885b n/a (libgallium-25.0.4.so + 0x55885b)
#6 0x00007f63b1b8cb77 n/a (libgallium-25.0.4.so + 0x58cb77)
#7 0x00007f63bee99546 start_thread (libc.so.6 + 0x99546)
#8 0x00007f63bef1d94c __clone3 (libc.so.6 + 0x11d94c)
Repeated ad nauseam after the first few traces. Then there’s this following directly after, which may be more useful:
May 03 18:26:01 localhost.localdomain systemd[1]: systemd-coredump@15-10899-0.service: Deactivated successfully.
May 03 18:26:01 localhost.localdomain sddm-helper[10812]: [PAM] Closing session
May 03 18:26:01 localhost.localdomain sddm-helper[10812]: pam_unix(sddm-greeter:session): session closed for user sddm
May 03 18:26:01 localhost.localdomain sddm-helper[10812]: pam_kwallet5(sddm-greeter:session): pam_kwallet5: pam_sm_close_session
May 03 18:26:01 localhost.localdomain sddm-helper[10812]: [PAM] Ended.
May 03 18:26:01 localhost.localdomain sddm[1412]: Auth: sddm-helper exited with 11
May 03 18:26:01 localhost.localdomain sddm[1412]: Greeter stopped. SDDM::Auth::HelperExitStatus(11)
May 03 18:26:01 localhost.localdomain systemd[1]: session-9.scope: Deactivated successfully.
May 03 18:26:01 localhost.localdomain systemd[1]: session-9.scope: Consumed 1.300s CPU time.
May 03 18:26:01 localhost.localdomain systemd-logind[1159]: Session 9 logged out. Waiting for processes to exit.
May 03 18:26:01 localhost.localdomain systemd-logind[1159]: Removed session 9.
May 03 18:26:02 localhost.localdomain drkonqi-coredump-processor[10901]: "/usr/bin/sddm-greeter-qt6" 10827 "/var/lib/systemd/coredump/core.sddm-greeter-qt.463.c36c507cb1af4051babe890b28743e7d.10827.1746289560000000.zst"
May 03 18:26:02 localhost.localdomain drkonqi-coredump-processor[10901]: The socket path doesn't exist @ "/run/user/463/drkonqi-coredump-launcher"
May 03 18:26:02 localhost.localdomain systemd[1]: drkonqi-coredump-processor@15-10899-0.service: Deactivated successfully.
May 03 18:26:04 localhost.localdomain systemd[1]: Started Getty on tty4.
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 03 18:26:04 localhost.localdomain systemd[10815]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Wil>
May 03 18:26:04 localhost.localdomain sddm[1412]: Display server stopped.
May 03 18:26:04 localhost.localdomain sddm[1412]: Running display stop script QList("/usr/share/sddm/scripts/Xstop")
May 03 18:26:04 localhost.localdomain sddm[1412]: Socket server stopping...
May 03 18:26:04 localhost.localdomain sddm[1412]: Socket server stopped.
I ran sudo zypper dup and the problem resolved itself.
Huh.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.