After rebooting with the latest kernel under Debian/unstable (5.16.0-1-amd64) and logging in via lightdm, the machine got frozen. I managed to get my desktop by switching to a text console (Ctrl-Alt-F1), then back to VT7 (where Xorg is running).
In the journalctl logs: [...] Feb 09 13:56:28 cventin systemd[1]: Stopping Session c1 of User lightdm... Feb 09 13:56:28 cventin lightdm[966]: pam_unix(lightdm-greeter:session): session closed for user lightdm Feb 09 13:56:28 cventin systemd[1]: session-c1.scope: Deactivated successfully. Feb 09 13:56:28 cventin systemd[1]: Stopped Session c1 of User lightdm. Feb 09 13:56:28 cventin systemd[1]: session-c1.scope: Consumed 1.728s CPU time. Feb 09 13:56:28 cventin systemd-logind[714]: Removed session c1. Feb 09 13:56:28 cventin lightdm[1071]: pam_unix(lightdm:session): session opened for user vlefevre(uid=1000) by (uid=0) Feb 09 13:56:28 cventin systemd[1]: Created slice User Slice of UID 1000. Feb 09 13:56:28 cventin systemd[1]: Starting User Runtime Directory /run/user/1000... Feb 09 13:56:28 cventin pulseaudio[987]: Error opening PCM device hdmi:1,1: No such file or directory Feb 09 13:56:38 cventin systemd-timesyncd[479]: Initial synchronization to time server 62.210.244.146:123 (2.debian.pool.ntp.org). Feb 09 13:56:52 cventin systemd-logind[714]: Failed to start session scope session-2.scope: Connection timed out Feb 09 13:56:52 cventin systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Feb 09 13:56:52 cventin lightdm[1071]: pam_systemd(lightdm:session): Failed to create session: Connection timed out [...] Note: the "Error opening PCM device hdmi:1,1: No such file or directory" message is usual. So this is not the cause of the issue. And I can see a bit later: Feb 09 13:56:53 cventin kernel: traps: light-locker[1582] trap int3 ip:7ff8c2dedddf sp:7ffe165ef8f0 error:0 in libglib-2.0.so.0.7000.3[7ff8c2db0000+8b000] This was the first time I got such a trap, but I don't know whether it is related, and if it is, whether this is a cause or a consequence. I tried again by rebooting a few times, but couldn't reproduce the problem. Any idea of the cause? A bug somewhere? -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
