Hey everyone,
After the big update, whenever I’m restarting my PC, it freezes for about 2-3 min when you have to put your password. After that I have absolutely no problem with my PC.
I’m actually not sure if it’s a freeze or if it takes time for my keyboard and mouse to be connected.
For info I’m with the I3 community edition.
encrypted ? what filesystem?
No it’s not encryted and boot/efi is in vfat and the rest in ext4.
so “when you have to put your password” means lightdm login manager screen where it takes up to 3 minutes to get i3 showing up? and it is default config or changed ?
Yes it’s lightdm, sorry I didn’t remember the name and it is default.
Check the logs and see what is happening during the time when the login is running.
/var/log/lightdm/lightdm.log
p.e.
[+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.02s] DEBUG: Seat seat0: Creating display server of type x
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file>
[+0.02s] DEBUG: Using VT 7
[+0.02s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.02s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.02s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.02s] DEBUG: XServer 0: Launching X Server
[+0.02s] DEBUG: Launching process 483: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten t>
[+0.02s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.14s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.14s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+1.85s] DEBUG: Got signal 10 from process 483
[+1.85s] DEBUG: XServer 0: Got signal from X server :0
[+1.85s] DEBUG: XServer 0: Connecting to XServer :0
[+1.85s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+1.85s] DEBUG: Session pid=692: Started with service 'lightdm-greeter', username 'lightdm'
[+1.87s] DEBUG: Session pid=692: Authentication complete with return value 0: Success
[+1.87s] DEBUG: Seat seat0: Session authenticated, running command
[+1.87s] DEBUG: Session pid=692: Running command /usr/bin/lightdm-gtk-greeter
[+1.87s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+1.87s] DEBUG: Session pid=692: Logging to /var/log/lightdm/seat0-greeter.log
[+2.04s] DEBUG: Activating VT 7
[+2.04s] DEBUG: Activating login1 session c1
[+2.04s] DEBUG: Seat seat0 changes active session to c1
[+2.04s] DEBUG: Session c1 is already active
[+2.44s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false
[+2.78s] DEBUG: Greeter start authentication for ierrep
[+2.78s] DEBUG: Session pid=737: Started with service 'lightdm', username 'wadax'
[+2.78s] DEBUG: Session pid=737: Got 1 message(s) from PAM
[+2.78s] DEBUG: Prompt greeter with 1 message(s)
[+77.38s] DEBUG: Continue authentication
[+77.39s] DEBUG: Session pid=737: Authentication complete with return value 0: Success
Is it the message that blocks the authentification ?
strange output in a way… it should follow up with showing this:
[+7.01s] DEBUG: Greeter start authentication for joekamprad
[+7.01s] DEBUG: Session pid=1039: Started with service 'lightdm', username 'joekamprad'
[+7.02s] DEBUG: Session pid=1039: Got 1 message(s) from PAM
[+7.02s] DEBUG: Prompt greeter with 1 message(s)
[+191.45s] DEBUG: Continue authentication
[+191.46s] DEBUG: Session pid=1039: Authentication complete with return value 0: Success
[+191.46s] DEBUG: Authenticate result for user joekamprad: Success
[+191.46s] DEBUG: User joekamprad authorized
[+191.47s] DEBUG: Greeter requests session i3
[+191.47s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+77.38s] DEBUG: Continue authentication
[+77.39s] DEBUG: Session pid=737: Authentication complete with return value 0: Success
[+77.39s] DEBUG: Authenticate result for user wadax: Success
[+77.39s] DEBUG: User wadax authorized
[+77.40s] DEBUG: Greeter sets language en_US.utf8
[+77.44s] DEBUG: Greeter requests session i3
[+77.44s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+77.44s] DEBUG: Terminating login1 session c1
[+77.44s] DEBUG: Session pid=692: Sending SIGTERM
[+77.46s] DEBUG: Greeter closed communication channel
[+77.46s] DEBUG: Session pid=692: Exited with return value 0
[+77.46s] DEBUG: Seat seat0: Session stopped
[+77.46s] DEBUG: Seat seat0: Greeter stopped, running session
[+77.46s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+77.46s] DEBUG: Session pid=737: Running command /etc/lightdm/Xsession i3
[+77.46s] DEBUG: Creating shared data directory /var/lib/lightdm-data/wadax
[+77.46s] DEBUG: Session pid=737: Logging to .xsession-errors
[+77.65s] DEBUG: Activating VT 7
[+77.65s] DEBUG: Activating login1 session 2
[+77.65s] DEBUG: Seat seat0 changes active session to
[+77.65s] DEBUG: Seat seat0 changes active session to 2
[+77.65s] DEBUG: Session 2 is already active
Sorry I didn’t put the entire debug log, I thought the beginning would be enough.
so this one looks totally normal…
the warning about Plymouth is normal as it is not used …
So it’s not lightdm, could it be linked to some hardware detection that take longer than before ?
not that long and not in this stage…
as you say it stuck for minutes when you try to login to a very light environment (i3) …
There is no hardware detection running anymore GPU and drivers p.e. are fully running and initialized.
In this stage it is only staring stuff from /etc/xdg/aurostart and what you have enabled in settings to get started with i3…
The journal from that timespan could give a hint, but includes in ost cases also a lot of uuids and personal information you should not post public without reviewing it … you can check with filtering it…
journalctl --since "5 minutes ago" per example right after your are logged in to i3 session… if you want you can send me in a P.M. so I can review the log…
try starting i3 without dex commenting the line in config:
~/.config/i3/config
#exec --no-startup-id dex --autostart --environment i3