Package: sddm Version: 0.14.0-4 Dear maintainer team,
I am running an up-to-date, plain-vanilla Debian 9 Stretch (i386) with a read-only root filesystem. During the boot process, an encrypted filesystem is mounted at /home. Sddm is configured to automatically login. However, this automatic login fails very often, because /home is very often not yet available when sddm tries to log in. See the excerpt from the log below. I am using "Linux XXX 4.9.0-4-686-pae #1 SMP Debian 4.9.51-1 (2017-09-28) i686 GNU/Linux", the /home filesystem is listed in /etc/crypttab and /etc/fstab. My suggested behavior would be to wait for a limited amount of time before the automatic login is executed / fails. Thanks for all your efforts in advance. Best regards, Ralf -------------------------------------------- Nov 04 11:41:57 XXX systemd[1]: Starting Cryptography Setup for home... -- Subject: Unit systemd-cryptsetup@home.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-cryptsetup@home.service has begun starting up. ... Nov 04 11:42:05 XXX systemd[1]: Started User Manager for UID 1005. -- Subject: Unit user@1005.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit user@1005.service has finished starting up. -- -- The start-up result is done. Nov 04 11:42:05 XXX sddm-helper[869]: Starting: "/etc/sddm/Xsession /usr/bin/startkde" Nov 04 11:42:05 XXX sddm-helper[874]: chdir( /home/YYY ) failed for user: "YYY" Nov 04 11:42:05 XXX sddm-helper[869]: pam_unix(sddm-autologin:session): session closed for user YYY Nov 04 11:42:05 XXX sddm-helper[874]: verify directory exist and has sufficient permissions Nov 04 11:42:05 XXX sddm[814]: Session started Nov 04 11:42:05 XXX sddm-helper[869]: [PAM] Closing session Nov 04 11:42:05 XXX sddm-helper[869]: [PAM] Ended. Nov 04 11:42:05 XXX sddm[814]: Auth: sddm-helper exited with 3 Nov 04 11:42:05 XXX sddm[814]: Display server stopping... Nov 04 11:42:05 XXX systemd-logind[470]: Removed session 1. -- Subject: Session 1 has been terminated -- Defined-By: systemd -- Support: https://www.debian.org/support -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A session with the ID 1 has been terminated. Nov 04 11:42:06 XXX systemd[1]: Stopping User Manager for UID 1005... -- Subject: Unit user@1005.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit user@1005.service has begun shutting down. ... Nov 04 11:42:06 XXX systemd[1]: Started Cryptography Setup for home. -- Subject: Unit systemd-cryptsetup@home.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-cryptsetup@home.service has finished starting up. -- -- The start-up result is done. Nov 04 11:42:06 XXX systemd[1]: Found device /dev/mapper/home. -- Subject: Unit dev-mapper-home.device has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit dev-mapper-home.device has finished starting up. -- -- The start-up result is done. Nov 04 11:42:06 XXX systemd[1]: Starting File System Check on /dev/mapper/home... -- Subject: Unit systemd-fsck@dev-mapper-home.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-fsck@dev-mapper-home.service has begun starting up. Nov 04 11:42:06 XXX systemd-fsck[902]: /dev/mapper/home: sauber, 64728/366528 Dateien, 664199/749743 Blöcke Nov 04 11:42:06 XXX systemd[1]: Started File System Check on /dev/mapper/home. -- Subject: Unit systemd-fsck@dev-mapper-home.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-fsck@dev-mapper-home.service has finished starting up. -- -- The start-up result is done. Nov 04 11:42:06 XXX systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. -- Subject: Mount point is not empty -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The directory /home is specified as the mount point (second field in -- /etc/fstab or Where= field in systemd unit file) and is not empty. -- This does not interfere with mounting, but the pre-exisiting files in -- this directory become inaccessible. To see those over-mounted files, -- please manually mount the underlying file system to a secondary -- location. Nov 04 11:42:06 XXX systemd[1]: Mounting /home... -- Subject: Unit home.mount has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit home.mount has begun starting up. Nov 04 11:42:06 XXX kernel: EXT4-fs (dm-2): mounting ext3 file system using the ext4 subsystem Nov 04 11:42:06 XXX kernel: EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) Nov 04 11:42:06 XXX systemd[1]: Mounted /home. -- Subject: Unit home.mount has finished start-up
