Package: libsystemd-login0 Version: 204-5 Severity: important Dear Maintainer,
Login is taking something like 20 seconds (while the rest of the boot was done after 9 seconds). Looking into dmesg, it does not report anything being done before systemd-login reports the "new seat". [ 9.817328] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 9.817450] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO [ 9.817505] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 33.275975] systemd-logind[2789]: New seat seat0. [ 33.277445] systemd-logind[2789]: Watching system buttons on /dev/input/event15 (Video Bus) [ 33.277641] systemd-logind[2789]: Watching system buttons on /dev/input/event9 (Power Button) [ 33.277823] systemd-logind[2789]: Watching system buttons on /dev/input/event3 (Lid Switch) [ 33.278009] systemd-logind[2789]: Watching system buttons on /dev/input/event10 (Sleep Button) [ 33.279761] systemd-logind[2789]: New session c1 of user manu. TRying with two differents DMs and without DM got similar results: The above timing is with lightdm. With lightdm, after 9 seconds, black screen appears and only 20 seconds later does the login window appear. With slim, the login screen appears fast but login never ends. Without a dm, loging in in a console goes OK but blocks at the MOTD for a long time before I get a prompt. The bug may not be with systemd-login but I do not know better! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (700, 'unstable'), (650, 'testing'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libsystemd-login0:amd64 depends on: ii libc6 2.17-93 ii multiarch-support 2.17-93 libsystemd-login0:amd64 recommends no packages. libsystemd-login0:amd64 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
