On 2022-05-25 13:35:27 +0200, Michael Biebl wrote: > I'm not really familiar with lightdm and I don't see any such issue > with gdm3.
Well, this doesn't mean anything. I've just looked at what I obtain on another machine (my laptop), which also now has systemd 251-2: May 24 10:26:21 zira systemd[1]: Starting User Login Management... May 24 10:26:22 zira systemd-logind[900]: New seat seat0. May 24 10:26:22 zira systemd-logind[900]: Watching system buttons on /dev/input/event9 (Power Button) May 24 10:26:22 zira systemd-logind[900]: Watching system buttons on /dev/input/event8 (Lid Switch) May 24 10:26:22 zira systemd-logind[900]: Watching system buttons on /dev/input/event7 (Sleep Button) May 24 10:26:22 zira systemd-logind[900]: Watching system buttons on /dev/input/event3 (Apple, Inc Apple Keyboard) May 24 10:26:22 zira systemd-logind[900]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard) May 24 10:26:22 zira systemd-logind[900]: Watching system buttons on /dev/input/event11 (HP WMI hotkeys) May 24 10:26:22 zira systemd[1]: Started User Login Management. May 24 10:26:27 zira systemd-logind[900]: New session c1 of user lightdm. So this seems to be hardware dependent. The issue seems to be that the "Watching system buttons on" lines now occur much later than expected on the other machine. Or actually, lightdm seems to start much earlier: With systemd 250.4-1: May 24 14:12:15 cventin kernel: microcode: microcode updated early to revision 0x49, date = 2021-08-11 [...] May 24 14:12:23 cventin systemd[1]: Starting User Login Management... i.e. an 8-second delay. With systemd 251-2: May 24 14:17:47 cventin kernel: microcode: microcode updated early to revision 0x49, date = 2021-08-11 [...] May 24 14:17:48 cventin systemd[1]: Starting User Login Management... i.e. a 1-second delay. > So I'm going to reassign this issue tentatively to lightdm, as its > maintainer will probably be in a better positition to help you get proper > debug logs from lightdm. I had looked at lightdm logs, but couldn't find anything useful. So, if I understand correctly, systemd now starts the user login management very early, possibly before the hardware is ready. If this is regarded as correct, does this mean that lightdm should have code to detect when a keyboard is ready? -- 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)
