On 2022-06-27 15:39:51 +0200, Vincent Lefevre wrote: [...] > but systemd-logind logged about the keyboard 10 seconds after the > boot, thus 5 seconds *after* the display manager was started: > > Jun 24 17:21:26 cventin systemd-logind[606]: Watching system buttons on > /dev/input/event2 (DELL Dell USB Entry Keyboard) > > So, what happens with systemd-logind there?
Just in case: cventin:~> systemd-analyze blame 10.812s NetworkManager-wait-online.service 2.341s loadcpufreq.service 1.298s nvidia-persistenced.service 1.204s gpm.service 716ms accounts-daemon.service 669ms avahi-daemon.service 607ms cups.service 565ms dev-sda5.device 519ms atd.service 516ms atopacct.service 445ms systemd-journal-flush.service 441ms lightdm.service 431ms e2scrub_reap.service 430ms lm-sensors.service 399ms polkit.service 392ms cpufrequtils.service 362ms systemd-modules-load.service 352ms mcelog.service 346ms rtkit-daemon.service 342ms udisks2.service 341ms atop.service 325ms dbus.service 322ms ModemManager.service 320ms systemd-udev-trigger.service 291ms systemd-logind.service 276ms exim4.service 249ms apparmor.service 192ms user@118.service 179ms user@1000.service 168ms rsyslog.service 153ms systemd-journald.service 150ms ssh.service 140ms systemd-udevd.service 137ms apache2.service 134ms colord.service 125ms apache-htcacheclean.service 117ms lvm2-monitor.service 106ms NetworkManager.service 103ms keyboard-setup.service [...] but the machine has 12 cores and I don't see a relation with systemd-logind. -- Vincent Lefèvre <vinc...@vinc17.net> - 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)
