Arch Linux: Lock screen frozen/unresponsive to login attempts

zhihuiyuze · 2026-03-12 20:03:48

My Arch Linux froze on the lock screen. After I type in my password, the login button doesn't respond, though I can still move the mouse.

I can switch to other TTYs using Ctrl + Alt + F1-F10, but I still can't log in from there. I’ve searched online and suspect it might be an issue with NVIDIA and Wayland, but the suggestions I found didn't solve my problem.

Below are the logs. Thank you to the community for your continued support and help.

 journalctl -p 3 -b -1

3月 12 06:27:46 archlinux kernel: RDSEED32 is broken. Disabling th
e corresponding CPUID bit.
3月 12 06:27:46 archlinux kernel: amd_gpio AMDI0030:00: Failed to 
request GPIO for pin 0x0000, err -EBUSY
3月 12 06:27:46 archlinux kernel: ACPI BIOS Error (bug): Could not
 resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20250807/psargs-332)
3月 12 06:27:46 archlinux kernel: ACPI Error: Aborting method \_TZ
.THRM._SCP due to previous error (AE_NOT_FOUND) (20250807/psparse-529)
3月 12 06:27:51 archlinux-laptop.huize.org kernel: 
3月 12 06:27:51 archlinux-laptop.huize.org kernel: platform acp_as
oc_acp70.0: warning: No matching ASoC machine driver found
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_check_protocol: Incompatible firmware protocol major 7 minor 2

3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_hw_start: firmware is not alive
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_smu_exec: smu cmd 4 failed, 0xff
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_smu_fini: Power off failed, ret -22
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_init: start npu failed, ret -22
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* amdxdna_probe: Hardware init failed, ret -22
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: probe with driver amdxdna failed with error -22
3月 12 06:27:51 archlinux-laptop.huize.org systemd-pcrextend[687]: 
Failed to unseal secret using TPM2: No such device or address
3月 12 06:27:52 archlinux-laptop.huize.org systemd-tpm2-setup[689]: 
Failed to unseal secret using TPM2: No such device or address
3月 12 06:27:52 archlinux-laptop.huize.org systemd-tpm2-setup[689]: 
Failed to acquire anchor secret: No such device or address
3月 12 06:27:52 archlinux-laptop.huize.org systemd[1]: Failed to s
tart Early TPM SRK Setup.
3月 12 06:27:53 archlinux-laptop.huize.org systemd-tpm2-setup[958]: 
Failed to unseal secret using TPM2: No such device or address
3月 12 06:27:53 archlinux-laptop.huize.org systemd-tpm2-setup[958]: 
Failed to acquire anchor secret: No such device or address
3月 12 06:27:53 archlinux-laptop.huize.org systemd[1]: Failed to s
tart TPM SRK Setup.
3月 12 06:27:54 archlinux-laptop.huize.org bluetoothd[1036]: Faile
d to set default system config for hci0
archlinux-laptop% journalctl -p 3 -b -1     
3月 12 06:27:46 archlinux kernel: RDSEED32 is broken. Disabling th
e corresponding CPUID bit.
3月 12 06:27:46 archlinux kernel: amd_gpio AMDI0030:00: Failed to 
request GPIO for pin 0x0000, err -EBUSY
3月 12 06:27:46 archlinux kernel: ACPI BIOS Error (bug): Could not
 resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20250807/psargs-332)
3月 12 06:27:46 archlinux kernel: ACPI Error: Aborting method \_TZ
.THRM._SCP due to previous error (AE_NOT_FOUND) (20250807/psparse-529)
3月 12 06:27:51 archlinux-laptop.huize.org kernel: 
3月 12 06:27:51 archlinux-laptop.huize.org kernel: platform acp_as
oc_acp70.0: warning: No matching ASoC machine driver found
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_check_protocol: Incompatible firmware protocol major 7 minor 2

3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_hw_start: firmware is not alive
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_smu_exec: smu cmd 4 failed, 0xff
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_smu_fini: Power off failed, ret -22
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* aie2_init: start npu failed, ret -22
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: [drm] *ERROR* amdxdna_probe: Hardware init failed, ret -22
3月 12 06:27:51 archlinux-laptop.huize.org kernel: amdxdna 0000:67
:00.1: probe with driver amdxdna failed with error -22
3月 12 06:27:51 archlinux-laptop.huize.org systemd-pcrextend[687]: 
Failed to unseal secret using TPM2: No such device or address
3月 12 06:27:52 archlinux-laptop.huize.org systemd-tpm2-setup[689]: 
Failed to unseal secret using TPM2: No such device or address
3月 12 06:27:52 archlinux-laptop.huize.org systemd-tpm2-setup[689]: 
Failed to acquire anchor secret: No such device or address
3月 12 06:27:52 archlinux-laptop.huize.org systemd[1]: Failed to s
tart Early TPM SRK Setup.
3月 12 06:27:53 archlinux-laptop.huize.org systemd-tpm2-setup[958]: 
Failed to unseal secret using TPM2: No such device or address
3月 12 06:27:53 archlinux-laptop.huize.org systemd-tpm2-setup[958]: 
Failed to acquire anchor secret: No such device or address
3月 12 06:27:53 archlinux-laptop.huize.org systemd[1]: Failed to s
tart TPM SRK Setup.
3月 12 06:27:54 archlinux-laptop.huize.org bluetoothd[1036]: Faile
d to set default system config for hci0
3月 12 17:44:31 archlinux-laptop.huize.org kwin_wayland[1456]: Libinput: event19 - ASCP1200:00 093A:3016 Touchpad: kernel bug: Tou
ch jump detected and discarded.
                                                                See https://wayland.freedesktop.org/libinput/doc/1.30.1/touchpad-jumping-cursors.h
tml for details
3月 12 17:45:12 archlinux-laptop.huize.org kwin_wayland[1456]: Libinput: event19 - ASCP1200:00 093A:3016 Touchpad: kernel bug: Tou
ch jump detected and discarded.
                                                                See https://wayland.freedesktop.org/libinput/doc/1.30.1/touchpad-jumping-cursors.h
tml for details
3月 12 17:45:12 archlinux-laptop.huize.org kwin_wayland[1456]: Libinput: event19 - ASCP1200:00 093A:3016 Touchpad: kernel bug: Tou
ch jump detected and discarded.
                                                                See https://wayland.freedesktop.org/libinput/doc/1.30.1/touchpad-jumping-cursors.h
tml for details
3月 12 17:45:12 archlinux-laptop.huize.org kwin_wayland[1456]: Libinput: event19 - ASCP1200:00 093A:3016 Touchpad: kernel bug: Tou
ch jump detected and discarded.
                                                                See https://wayland.freedesktop.org/libinput/doc/1.30.1/touchpad-jumping-cursors.h
tml for details
3月 12 17:45:15 archlinux-laptop.huize.org kwin_wayland[1456]: Libinput: event19 - ASCP1200:00 093A:3016 Touchpad: kernel bug: Tou
ch jump detected and discarded.
                                                                See https://wayland.freedesktop.org/libinput/doc/1.30.1/touchpad-jumping-cursors.h
tml for details
3月 12 17:45:15 archlinux-laptop.huize.org kwin_wayland[1456]: Libinput: event19 - ASCP1200:00 093A:3016 Touchpad: WARNING: log ra
te limit exceeded (5 msgs per 24h). Discarding future messages.
3月 12 18:20:19 archlinux-laptop.huize.org systemd-coredump[25908]: [?] Process 25897 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1737:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:20:20 archlinux-laptop.huize.org systemd-coredump[25945]: [?] Process 25936 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1745:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:20:21 archlinux-laptop.huize.org systemd-coredump[25973]: [?] Process 25963 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1754:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:20:31 archlinux-laptop.huize.org systemd-coredump[26022]: [?] Process 26013 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1782:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:20:31 archlinux-laptop.huize.org systemd-coredump[26044]: [?] Process 26035 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1790:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:20:32 archlinux-laptop.huize.org systemd-coredump[26064]: [?] Process 26054 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1798:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:20:32 archlinux-laptop.huize.org systemd-coredump[26086]: [?] Process 26077 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1806:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fa3b8d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fa888b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:20:33 archlinux-laptop.huize.org systemd-coredump[26109]: [?] Process 26099 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1814:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fa3b8d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fa888b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:20:34 archlinux-laptop.huize.org systemd-coredump[26136]: [?] Process 26126 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1822:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625f9b58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fa028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:20:34 archlinux-laptop.huize.org systemd-coredump[26158]: [?] Process 26149 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1831:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fa3b8d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fa888b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:23:39 archlinux-laptop.huize.org systemd-coredump[26362]: [?] Process 26353 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1871:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fa3b8d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fa888b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:23:40 archlinux-laptop.huize.org systemd-coredump[26382]: [?] Process 26370 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1879:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:23:40 archlinux-laptop.huize.org systemd-coredump[26414]: [?] Process 26404 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1889:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:23:41 archlinux-laptop.huize.org systemd-coredump[26441]: [?] Process 26431 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1897:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 18:23:42 archlinux-laptop.huize.org systemd-coredump[26463]: [?] Process 26454 (yandex_browser) of use
r 1000 dumped core.
                                                                     
                                                                     Stack trace of thread 1905:
                                                                     #0  0x00007f6269b2c51c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9c51c)
                                                                     #1  0x00007f6269ad23be n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x423be)
                                                                     #2  0x00007f6269ab98ed n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x298ed)
                                                                     #3  0x00007f6269aba958 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a958)
                                                                     #4  0x00007f6269b1f7e9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f7e9)
                                                                     #5  0x00007f6269b2d3f0 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9d3f0)
                                                                     #6  0x00007f625fbb58d9 n/a (/usr/lib/x86_64-linux-gnu/GL/nvidia-590-48-01/lib
/libnvidia-glsi.so.590.48.01 + 0x408d9)
                                                                     #7  0x5fc028b800007f62 n/a (n/a + 0x0)
                                                                     ELF object binary architecture: AMD x86-64
3月 12 19:03:40 archlinux-laptop.huize.org kernel: [drm:__nv_drm_semsurf_wait_fence_work_cb [nvidia_drm]] *ERROR* [nvidia-drm] [GP
U ID 0x00006500] Failed to register auto-value-update on pre-wait value for sync FD semaphore surface
3月 12 22:10:48 archlinux-laptop.huize.org kscreenlocker_greet[29601]: pam_faillock(kde:auth): Error sending audit message: 不允许
的操作
3月 12 22:10:48 archlinux-laptop.huize.org kscreenlocker_greet[29601]: pam_faillock(kde:auth): Error sending audit message: 不允许
的操作
3月 12 22:10:58 archlinux-laptop.huize.org kscreenlocker_greet[29601]: [PAM worker kde] Authentication attempt too soon. This shou
ldn't happen!

xerxes_ · 2026-03-13 21:56:44

Post more about your hardware: what CPU (some AMD?), what nvidia card (you may have drivers not for your card), what laptop model?
Do you have microcode installed for your CPU and firmware for your hardware components?
I see you use KDE on Wayland, but KDE have some issues recently... Maybe try other DE on Wayland, like sway, for test?
It would be good if you post full journalctl log.
And something I don't understand: you wrote that you can't login but yandex_browser is trying to start and already crashing?

seth · 2026-03-13 22:25:05

I can switch to other TTYs using Ctrl + Alt + F1-F10, but I still can't log in from there.

How exactly does that context fail? Also freezing?

journalctl -p 3 -b -1

Please post your complete system journal for the boot w/ the failing login, eg. for the current boot

sudo journalctl -b | curl -F 'file=@-' 0x0.st

(this will also take care of the formatting)

zhihuiyuze · Yesterday 18:32:22

xerxes_ wrote:

Post more about your hardware

System:
  Kernel: 6.19.6-arch1-1.1-g14 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: KDE Plasma v: 6.6.2 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A16 FA608WI_FA608WI
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FA608WI v: 1.0 serial: <superuser required>
    Firmware: UEFI vendor: American Megatrends LLC. v: FA608WI.309
    date: 10/01/2025
Battery:
  ID-1: BAT1 charge: 64.8 Wh (83.2%) condition: 77.9/90 Wh (86.5%)
    volts: 16.44 min: 15.93 model: ASUS A32-K55 serial: N/A charging:
    status: not charging cycles: N/A
CPU:
  Info: 12-core model: AMD Ryzen AI 9 HX 370 w/ Radeon 890M bits: 64
    type: MT MCP arch: Zen 5 rev: 0 cache: L1: 960 KiB L2: 12 MiB L3: 24 MiB
  Speed (MHz): avg: 5138 min/max: 605/5158:3289 boost: enabled cores:
    1: 5138 2: 5138 3: 5138 4: 5138 5: 5138 6: 5138 7: 5138 8: 5138 9: 5138
    10: 5138 11: 5138 12: 5138 13: 5138 14: 5138 15: 5138 16: 5138 17: 5138
    18: 5138 19: 5138 20: 5138 21: 5138 22: 5138 23: 5138 24: 5138
    bogomips: 95814
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile] vendor: ASUSTeK
    driver: nvidia v: 590.48.01 arch: Lovelace pcie: speed: 16 GT/s lanes: 8
    ports: active: none empty: DP-9,HDMI-A-1,eDP-2 bus-ID: 65:00.0
    chip-ID: 10de:2860
  Device-2: Advanced Micro Devices [AMD/ATI] Strix [Radeon 880M / 890M]
    vendor: ASUSTeK driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16
    ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7,
    DP-8, Writeback-1 bus-ID: 66:00.0 chip-ID: 1002:150e temp: 42.0 C
  Device-3: Sonix ASUS FHD webcam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-1:2 chip-ID: 3277:0018
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositors: 1: kwin_wayland 2: Tabby driver: X: loaded: amdgpu
    dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: BOE Display NE160QDM-NYJ res: 2560x1600 hz: 165
    dpi: 189 diag: 406mm (16")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: radeonsi
    device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland:
    drv: nvidia x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 26.0.1-arch1.1
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4070 Laptop
    GPU/PCIe/SSE2 display-ID: :1.0
  API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu
    driver: nvidia device-ID: 10de:2860 device: 1 type: integrated-gpu
    driver: mesa radv device-ID: 1002:150e
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: NVIDIA AD106M High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 8
    bus-ID: 65:00.1 chip-ID: 10de:22bd
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 66:00.1 chip-ID: 1002:1640
  Device-3: Advanced Micro Devices [AMD] Audio Coprocessor
    driver: snd_acp_pci v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 66:00.5
    chip-ID: 1022:15e2
  Device-4: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 66:00.6 chip-ID: 1022:15e3
  API: ALSA v: k6.19.6-arch1-1.1-g14 status: kernel-api
  Server-1: sndiod v: N/A status: off
  Server-2: JACK v: 1.9.22 status: off
  Server-3: PipeWire v: 1.6.0 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Foxconn driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 62:00.0 chip-ID: 14c3:0616
  IF: wlp98s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: f000 bus-ID: 63:00.0 chip-ID: 10ec:8168
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: ztfl6g42vh state: unknown speed: 10000 Mbps duplex: full
    mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 3-3:4 chip-ID: 0489:e0f6
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 4.66 TiB used: 1.59 TiB (34.1%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL81T0HELB-00BTW
    size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 28.9 C
  ID-2: /dev/nvme1n1 model: Predator SSD GM9000 4TB size: 3.73 TiB
    speed: 126 Gb/s lanes: 4 serial: <filter> temp: 41.9 C
Partition:
  ID-1: / size: 934.06 GiB used: 62.98 GiB (6.7%) fs: bcachefs dev: /dev/dm-1
    mapped: vg0-root
  ID-2: /boot size: 2 GiB used: 613.4 MiB (30.0%) fs: vfat
    dev: /dev/nvme1n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A gpu: amdgpu temp: 42.0 C
  Fan Speeds (rpm): cpu: 3000 fan-1: 3080
Info:
  Memory: total: 32 GiB note: est. available: 30.41 GiB used: 18.7 GiB (61.5%)
  Processes: 655 Power: uptime: 1d 22h 34m wakeups: 10 Init: systemd v: 259
    default: graphical
  Packages: 1346 pm: pacman pkgs: 1333 pm: flatpak pkgs: 13 Compilers:
    gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.40

xerxes_ wrote:

And something I don't understand: you wrote that you can't login but yandex_browser is trying to start and already crashing?

No, I can login most of the times, but sometimes when I close the screen or the laptop is auto lock the thing happens

seth wrote:

I can switch to other TTYs using Ctrl + Alt + F1-F10, but I still can't log in from there.
How exactly does that context fail? Also freezing?
journalctl -p 3 -b -1
Please post your complete system journal for the boot w/ the failing login, eg. for the current boot
sudo journalctl -b | curl -F 'file=@-' 0x0.st
(this will also take care of the formatting)

For this, should I wait until the next freezing, while the system cannot be unlocked, until I log in?

The log here is for now, but it is not the log from the boot after the crash.

https://0x0.st/PLTq.txt

seth · Yesterday 20:38:20

For this, should I wait until the next freezing, while the system cannot be unlocked, until I log in?

You can access and post older logs, if they cover such incident (-b -δ, bigger δ means older boot)

zhihuiyuze · Yesterday 21:26:28

archlinux-laptop% journalctl -p 3 -b -1
archlinux-laptop% uptime
 01:23:41 up 2 days,  1:34,  1 user,  load average: 1.22, 1.30, 1.26
archlinux-laptop%

Ok, it is actually just the last boot,

 3月 12 22:10:48 archlinux-laptop.huize.org kscreenlocker_greet[29601]: pam_faillock(kde:auth): Error sending audit message: 不允许
的操作

here is showing it can't be unlocked. in english March 12, 22:10:48 archlinux-laptop.huize.org kscreenlocker_greet[29601]: pam_faillock(kde:auth): Error sending audit message: Operation not allowed.

Full logs are here.

https://0x0.st/PLaq.txt

seth · Yesterday 21:35:25

3月 12 19:03:40 archlinux-laptop.huize.org kernel: [drm:__nv_drm_semsurf_wait_fence_work_cb [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00006500] Failed to register auto-value-update on pre-wait value for sync FD semaphore surface
3月 12 22:10:48 archlinux-laptop.huize.org kscreenlocker_greet[29601]: pam_faillock(kde:auth): Error sending audit message: 不允许的操作
3月 12 22:10:48 archlinux-laptop.huize.org kscreenlocker_greet[29601]: pam_faillock(kde:auth): Error sending audit message: 不允许的操作
3月 12 22:10:58 archlinux-laptop.huize.org kscreenlocker_greet[29601]: [PAM worker kde] Authentication attempt too soon. This shouldn't happen!

The gap ahead of faillock is > 3h, please post the entire journal

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

However https://bugs.kde.org/show_bug.cgi?id=504962
Generally see https://wiki.archlinux.org/title/Securi … n_attempts - the root account is not affected by this so you would always be able to login as root and free your user.
faillock is often triggered by background scripts trying to run sudo etc. but you could just have fumbled the password and then run into the KDE bug

zhihuiyuze · Yesterday 21:43:53

I don't think it was caused by me entering the wrong password, because if it were, the lockout page would show that I'm locked and need to wait 10 minutes. What I experienced was that only the mouse was movable.

I checked the KDE bug report, I'll try entering the wrong password multiple times to see if that triggers the issue.

https://0x0.st/PLaJ.txt

zhihuiyuze · Yesterday 21:51:10

Yes entering the wrong password for many times can trigger SDDM only the mouse is movable.

But the last problem happened is that the SDDM and lock screen for KDE were in the same situation, now KDE lock screen works fine — showing too many password attempts, waits for 10 minutes. And the buttons are all working.

seth · Yesterday 21:57:20

3月 12 22:10:34 archlinux-laptop.huize.org org_kde_powerdevil[1741]: [  1847] Udev event detected
3月 12 22:10:35 archlinux-laptop.huize.org systemd[1]: Stopped target Suspend.
3月 12 22:10:35 archlinux-laptop.huize.org org_kde_powerdevil[1741]: [  1847] Udev event detected
3月 12 22:10:36 archlinux-laptop.huize.org kscreenlocker_greet[29601]: pam_unix(kde:auth): authentication failure; logname=huize uid=1000 euid=1000 tty= ruser= rhost=  user=huize
3月 12 22:10:36 archlinux-laptop.huize.org org_kde_powerdevil[1741]: [  1847] Udev event detected
3月 12 22:10:37 archlinux-laptop.huize.org org_kde_powerdevil[1741]: [  1847] Udev event detected
3月 12 22:10:48 archlinux-laptop.huize.org kscreenlocker_greet[29601]: pam_faillock(kde:auth): Error sending audit message: 不允许的操作

You're entering the wrong password at least once very quickly after the suspend - do you recall whether that might have happened?
Another explanation is that some chargers cause spurious input events, typically unkonwn and not handled keys but I wonder whether those might have triggered Enter (on an empty password input) and possibly as storm.

Last but not least, it's possibly entirely unrelated and caused by

3月 12 06:27:46 archlinux kernel: hid-generic 0003:3434:07F4.0002: input,hiddev96,hidraw1: USB HID v1.11 Joystick [Keychron  Keychron B36] on usb-0000:68:00.0-1/input1

https://bbs.archlinux.org/viewtopic.php?id=309989

zhihuiyuze · Yesterday 22:12:42

Now that I've re-entered the system, SDDM on tty2 is completely dead, though it hasn't affected KDE or the other TTYs (the non-GUI ones). I'm also using a Keychron keyboard—specifically the Keychron B36 Wireless.

I remember entering the password incorrectly myself the first time, but I'm not entirely sure—my memory is a bit fuzzy. If it were a keyboard mapping issue, shouldn't there be some visible input if I switch to a non-GUI TTY?

seth · Yesterday 22:27:16

If it were a keyboard mapping issue, shouldn't there be some visible input if I switch to a non-GUI TTY?

Depends on the actual key.
I know that you're using the keychron keyboard (the journal line specifically highlights the bogus joystick device)

The usually reliable trigger for that thing is to switch from an X11 session to a console TTY and then back to X11.
Unsetting ID_INPUT_JOYSTICK w/ a udev rule would typically prevent that problem

thakares · Today 07:47:59

GNOME Session Crashes on Lock Screen / Suspend-Resume (Ryzen 8000 Series / HawkPoint)

Symptoms

Session dies after screen lock or suspend, requiring hard reboot
GDM login screen appears instead of lock screen after resume
journalctl shows gdm.service: Failed with result 'exit-code'
gnome-keyring-daemon spawning twice on login/lock
NotInControl errors for /dev/input/event* in gnome-shell logs
(EE) failed to read Wayland events: Broken pipe in gnome-shell logs

Affected Hardware

Laptops with AMD Ryzen 8000 series (HawkPoint), e.g. Lenovo IdeaPad Slim 5 16AHP9
AMD Radeon 780M integrated graphics
GNOME 49 on Wayland, kernel 6.19+

Root Causes Found

After extensive journalctl analysis, the following independent issues were identified:

GNOME Keyring daemon spawning twice per session due to three simultaneous launch mechanisms (XDG autostart, GDM socket activation, D-Bus service activation) racing against socket activation
An orphan /usr/lib/systemd/system-sleep/gnome-shell-restart script (not owned by any package) sending SIGHUP to gnome-shell on every resume
broadcom-wl package loaded on hardware using MediaTek WiFi, tainting the kernel
Mutter experimental features (variable-refresh-rate, scale-monitor-framebuffer) causing KMS session handoff failures on AMD Wayland
amdgpu scatter-gather display causing resume instability on HawkPoint

Fix 1: GNOME Keyring Double-Spawn

Three separate mechanisms were independently launching duplicate keyring daemon instances into every session including GDM's greeter, causing PAM authentication races.

1a. Suppress XDG autostart system-wide

Socket activation via gnome-keyring-daemon.socket handles the daemon correctly. Suppress the redundant XDG autostart entries:

sudo ln -sf /dev/null /etc/xdg/autostart/gnome-keyring-secrets.desktop
sudo ln -sf /dev/null /etc/xdg/autostart/gnome-keyring-pkcs11.desktop

1b. Mask keyring socket for GDM greeter

sudo mkdir -p /var/lib/gdm/.config/systemd/user/
sudo ln -sf /dev/null /var/lib/gdm/.config/systemd/user/gnome-keyring-daemon.socket
sudo chown -R gdm:gdm /var/lib/gdm/.config/

1c. Remove pam_gnome_keyring from GDM PAM stack

Edit /etc/pam.d/gdm-password and remove all three pam_gnome_keyring.so lines so it contains only:

#%PAM-1.0
auth       include                     system-local-login
account    include                     system-local-login
password   include                     system-local-login
session    include                     system-local-login

1d. Fix D-Bus service activation (most important)

Without a SystemdService= directive, D-Bus spawns a fresh daemon process every time any application requests the secrets service, bypassing socket activation entirely and causing a second instance to race with the socket-activated one.

Add SystemdService=gnome-keyring-daemon.service to each of these three files:

/usr/share/dbus-1/services/org.freedesktop.secrets.service
/usr/share/dbus-1/services/org.gnome.keyring.service
/usr/share/dbus-1/services/org.freedesktop.impl.portal.Secret.service

Each file should look like this (example for org.freedesktop.secrets.service):

[D-BUS Service]
Name=org.freedesktop.secrets
Exec=/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
SystemdService=gnome-keyring-daemon.service

Note: These files are owned by the gnome-keyring package and will be overwritten on package updates. Use a pacman hook or reapply after upgrades.

Fix 2: Remove Orphan gnome-shell Sleep Script

An unpackaged script was sending SIGHUP to gnome-shell on every resume from suspend, killing the Wayland compositor and all connected clients. First verify it is unpackaged:

pacman -Qo /usr/lib/systemd/system-sleep/gnome-shell-restart

If the output is "error: No package owns ...", remove it:

sudo rm /usr/lib/systemd/system-sleep/gnome-shell-restart

Fix 3: Remove Conflicting Broadcom WiFi Driver

The broadcom-wl package loads the wl kernel module which is wrong for the MediaTek WiFi hardware on HawkPoint laptops. It taints the kernel and can cause instability:

sudo pacman -Rs broadcom-wl

The correct driver mt7921e loads automatically.

Fix 4: Disable Mutter Experimental Features

GNOME 49 on Arch ships with experimental features enabled via /usr/share/glib-2.0/schemas/30_org.archlinux.gnome-shell.gschema.override. The features variable-refresh-rate and scale-monitor-framebuffer cause session crashes on AMD Wayland systems by interfering with KMS session handoff during lock/suspend.

gsettings set org.gnome.mutter experimental-features "[]"

Since the Arch schema override re-enables these on every login, create a higher-priority override:

sudo tee /usr/share/glib-2.0/schemas/99_disable-experimental.gschema.override << 'EOF'
[org.gnome.mutter:GNOME]
experimental-features=@as []
EOF
sudo glib-compile-schemas /usr/share/glib-2.0/schemas/

Note: This disables scale-monitor-framebuffer, variable-refresh-rate, and xwayland-native-scaling. Re-enable selectively once upstream stability improves for your hardware.

Fix 5: amdgpu Kernel Parameters for Stable Resume

Add to /etc/default/grub:

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet amdgpu.sg_display=0 amd_pstate=active"

Warning: Remove mem_sleep_default=s2idle if present — forcing s2idle explicitly causes instability on this hardware.

Regenerate GRUB config:

sudo grub-mkconfig -o /boot/grub/grub.cfg

Also add modprobe option:

echo "options amdgpu sg_display=0" | sudo tee /etc/modprobe.d/amdgpu.conf

Fix 6: Re-enable Lock Screen

gsettings set org.gnome.desktop.screensaver lock-enabled true

Known Remaining Issue: Lid Close Does Not Auto-Lock

On this hardware combination (AMD HawkPoint + GNOME 49 + Wayland + s2idle), gsd-power fails to complete lock screen activation before releasing its suspend inhibitor. Closing the lid without manually locking first results in an unlocked session on resume.

Workaround: Press Super+L before closing the lid.

This is a known upstream issue. Track progress at:

Verification

After all fixes, confirm clean state:

# Single keyring daemon instance
pgrep -f gnome-keyring-daemon

# No wl module loaded
lsmod | grep wl

# Kernel parameters active
cat /proc/cmdline

# Experimental features disabled
gsettings get org.gnome.mutter experimental-features

# Lock screen enabled
gsettings get org.gnome.desktop.screensaver lock-enabled

Last edited by thakares (Today 07:49:38)

seth · Today 08:19:17

After extensive journalctl analysis, the following independent issues were identified:

The journals clearly shows that the OP is using neither GDM, nor gnome nor GKR - your AI sucks.

Arch Linux

#1 2026-03-12 20:03:48