Arch Linux

subrkf

Member

Registered: 2024-10-03

Posts: 1

GDM lock screen kicks user into cannot-login state

The steps I have used to reliably recreate this on my machine are:

1) Log into my user.
2) Lock the screen, returning to the single-user GDM login dialog.
3) Wait a few seconds.

GDM goes through some graphical artifact, and ends up in the following state:

- TTY 1 is the multi-user login screen
- TTY 2 is the single-user locked login screen, but typing in the password will hang instead of entering the user

In this state, the user is still logged in and processes continue running, but I haven't found a way to actually re-enter the active gnome session. The only 'fix' is to `killall gnome-session-binary`, or some similar way of restarting gnome entirely.

I've attached journalctl logs below of two instances of this happening. I tried to disable most things (all extensions, fractional scaling).

https://pastebin.com/Yit5arFt
https://pastebin.com/uAFBz5Rr

Some other computer info:

dmidecode -t system

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: Framework
	Product Name: Laptop
	Version: AB
	Serial Number: FRANBMCPAB139100M4
	UUID: 62a2a150-831f-ec11-810d-222643700456
	Wake-up Type: Power Switch
	SKU Number: FRANBMCP0B
	Family: FRANBMCP

fastfetch

OS: Arch Linux x86_64
Host: Laptop (AB)
Kernel: Linux 6.11.1-arch1-1
Uptime: 38 mins
Packages: 2740 (pacman), 7 (flatpak)
Shell: bash 5.2.37
Display (BOE095F): 2256x1504 @ 60 Hz (as 1803x1202) in 13″ [Built-in]
DE: GNOME 47.0
WM: Mutter (Wayland)
WM Theme: Adwaita
Theme: Adwaita [GTK2/3/4]
Icons: Adwaita [GTK2/3/4]
Font: Cantarell (11pt) [GTK2/3/4]
Cursor: Adwaita (24px)
Terminal: guake
CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 (8) @ 4.70 GHz
GPU: Intel Iris Xe Graphics @ 1.30 GHz [Integrated]
Memory: 5.31 GiB / 31.14 GiB (17%)
Swap: Disabled
Disk (/): 1.16 TiB / 1.66 TiB (70%) - btrfs
Local IP (wlan0): 192.168.0.47/24
Locale: en_US.UTF-8

If there's any other information that would be helpful, let me know!