[Solved] [XFCE4] Desktop is displayed +5 min after login

[c.monty]

Hi,

I'm experiencing the following issue:
after login (LightDM) I must wait +5 min until the desktop is displayed.

There's no waiting time when logging out and the login again, means the issue only occurs when starting or rebooting.

This is the relevant log /var/log/lightdm/lightdm.log:

Code Select Expand

root@pc5-desktop:/home/thomas# tail -n 50 /var/log/lightdm/lightdm.log
[+1311.40s] DEBUG: Session pid=2869: Running command /usr/sbin/lightdm-gtk-greeter
[+1311.40s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+1311.40s] DEBUG: Session pid=2869: Logging to /var/log/lightdm/seat0-greeter.log
[+1312.12s] DEBUG: Activating VT 8
[+1312.12s] DEBUG: Locking login1 session 10
[+1312.13s] DEBUG: Activating login1 session c5
[+1312.14s] DEBUG: Seat seat0 changes active session to c5
[+1312.14s] DEBUG: Session c5 is already active
[+1313.14s] DEBUG: Greeter connected version=1.18.3 resettable=false
[+1315.67s] DEBUG: Greeter start authentication
[+1315.67s] DEBUG: Session pid=2908: Started with service 'lightdm', username '(null)'
[+1315.77s] DEBUG: Session pid=2908: Got 1 message(s) from PAM
[+1315.77s] DEBUG: Prompt greeter with 1 message(s)
[+1875.56s] DEBUG: Greeter start authentication for thomas
[+1875.56s] DEBUG: Session pid=2908: Sending SIGTERM
[+1875.56s] DEBUG: Seat seat0: Failed to work out session ID to mark
[+1875.56s] DEBUG: Session pid=3080: Started with service 'lightdm', username 'thomas'
[+1875.57s] DEBUG: Session pid=2908: Terminated with signal 15
[+1875.57s] DEBUG: Session: Failed during authentication
[+1875.57s] DEBUG: Seat seat0: Session stopped
[+1875.68s] DEBUG: Session pid=3080: Got 1 message(s) from PAM
[+1875.68s] DEBUG: Prompt greeter with 1 message(s)
[+1879.09s] DEBUG: Continue authentication
[+1879.17s] DEBUG: Session pid=3080: Authentication complete with return value 0: Success
[+1879.17s] DEBUG: Authenticate result for user thomas: Success
[+1879.18s] DEBUG: User thomas authorized
[+1879.21s] DEBUG: Greeter sets language de_DE.utf8
[+1879.30s] DEBUG: Greeter requests session lightdm-xsession
[+1879.30s] DEBUG: Seat seat0: Returning to existing user session thomas
[+1879.30s] DEBUG: Unlocking login1 session 10
[+1879.30s] DEBUG: Activating VT 7
[+1879.30s] WARNING: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call
[+1879.30s] DEBUG: Seat seat0: Stopping greeter
[+1879.30s] DEBUG: Session pid=2869: Sending SIGTERM
[+1879.30s] DEBUG: Activating login1 session 10
[+1879.31s] DEBUG: Session pid=3080: Exited with return value 0
[+1879.31s] DEBUG: Seat seat0: Session stopped
[+1879.36s] DEBUG: Greeter closed communication channel
[+1879.36s] DEBUG: Session pid=2869: Exited with return value 0
[+1879.36s] DEBUG: Seat seat0: Session stopped
[+1879.36s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1879.36s] DEBUG: Sending signal 15 to process 2855
[+1879.42s] DEBUG: Seat seat0 changes active session to
[+1879.50s] DEBUG: Process 2855 exited with return value 0
[+1879.50s] DEBUG: DisplayServer x-1: X server stopped
[+1879.50s] DEBUG: Releasing VT 8
[+1879.50s] DEBUG: DisplayServer x-1: Removing X server authority /var/run/lightdm/root/:1
[+1879.50s] DEBUG: Seat seat0: Display server stopped
[+1879.58s] DEBUG: Seat seat0 changes active session to 10
[+1879.58s] DEBUG: Session 10 is already active

How can I analyze the root cause further?

THX

[lami07]

Hi. You are not the only user struggling with this problem. Unfortunately the underlying issue is yet to be found. Personally I would advise changing kernel. My expirence shows that kernel 4.16 from Debian repo is free from this issue. Same goes for kernel 4.18 from sparky unstable repo.

[paxmark1]

post linux kernel (inxi works well) and post first few lines of

"systemd-analyze blame"


very well could be the kernel version. 

[c.monty]

Linux Kernel:

Code Select Expand

thomas@pc5-desktop:~$ sudo inxi -S
System:    Host: pc5-desktop Kernel: 4.17.0-2-amd64 x86_64 bits: 64 Console: tty 0
           Distro: SparkyLinux 5 (Nibiru)

Code Select Expand

thomas@pc5-desktop:~$ sudo systemd-analyze blame
          3.398s NetworkManager-wait-online.service
          3.345s dev-sda2.device
          1.919s exim4.service
          1.653s systemd-hwdb-update.service
          1.193s udisks2.service
          1.043s user@109.service
           860ms networking.service
           848ms ModemManager.service
           728ms keyboard-setup.service
           598ms systemd-journald.service
           525ms avahi-daemon.service
           519ms systemd-udev-trigger.service


After reproducing the issue log /var/log/lightdm/lightdm.log is displaying this info that confirms that waiting time:

Code Select Expand

thomas@pc5-desktop:~$ sudo tail -f /var/log/lightdm/lightdm.log
[+53.76s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+53.76s] DEBUG: Session pid=732: Sending SIGTERM
[+53.79s] DEBUG: Greeter closed communication channel
[+53.80s] DEBUG: Session pid=732: Exited with return value 0
[+53.80s] DEBUG: Seat seat0: Session stopped
[+53.80s] DEBUG: Seat seat0: Greeter stopped, running session
[+53.80s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+53.81s] DEBUG: Session pid=1311: Running command /etc/X11/Xsession default
[+53.81s] DEBUG: Creating shared data directory /var/lib/lightdm/data/manfred
[+53.81s] DEBUG: Session pid=1311: Logging to .xsession-errors
[+148.87s] DEBUG: Activating VT 7
[+148.87s] DEBUG: Activating login1 session 4
[+148.87s] DEBUG: Seat seat0 changes active session to
[+148.87s] DEBUG: Seat seat0 changes active session to 4
[+148.87s] DEBUG: Session 4 is already active
[+773.85s] DEBUG: Seat seat0: Locking
[+773.85s] DEBUG: Seat seat0: Creating greeter session
[+773.85s] DEBUG: Seat seat0: Creating display server of type x
[+773.85s] DEBUG: Using VT 8
[+773.85s] DEBUG: Seat seat0: Starting local X display on VT 8
[+773.85s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
[+773.85s] DEBUG: DisplayServer x-1: Writing X server authority to /var/run/lightdm/root/:1
[+773.85s] DEBUG: DisplayServer x-1: Launching X Server
[+773.85s] DEBUG: Launching process 1889: /usr/bin/X :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
[+773.85s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
[+774.06s] DEBUG: Seat seat0 changes active session to
[+775.01s] DEBUG: Got signal 10 from process 1889
[+775.01s] DEBUG: DisplayServer x-1: Got signal from X server :1
[+775.01s] DEBUG: DisplayServer x-1: Connecting to XServer :1
[+775.01s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+775.02s] DEBUG: Session pid=1902: Started with service 'lightdm-greeter', username 'lightdm'
[+775.12s] DEBUG: Session pid=1902: Authentication complete with return value 0: Success
[+775.12s] DEBUG: Seat seat0: Session authenticated, running command
[+775.12s] DEBUG: Session pid=1902: Running command /usr/sbin/lightdm-gtk-greeter
[+775.12s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+775.12s] DEBUG: Session pid=1902: Logging to /var/log/lightdm/seat0-greeter.log
[+775.72s] DEBUG: Activating VT 8
[+775.72s] DEBUG: Locking login1 session 4
[+775.73s] DEBUG: Activating login1 session c2
[+775.74s] DEBUG: Seat seat0 changes active session to c2
[+775.74s] DEBUG: Session c2 is already active
[+776.45s] DEBUG: Greeter connected version=1.18.3 resettable=false
[+778.80s] DEBUG: Greeter start authentication
[+778.80s] DEBUG: Session pid=1941: Started with service 'lightdm', username '(null)'
[+778.87s] DEBUG: Session pid=1941: Got 1 message(s) from PAM
[+778.87s] DEBUG: Prompt greeter with 1 message(s)


[c.monty]

Installing another kernel is not fixing the isse, means with this kernel 4.16.0-2-amd64 x86_64 from Debian Sid the same waittime is noticed:

Code Select Expand

thomas@pc5-desktop:~$ inxi -S
System:    Host: pc5-desktop Kernel: 4.16.0-2-amd64 x86_64 bits: 64 Desktop: N/A Distro: SparkyLinux 5 (Nibiru)

Code Select Expand

thomas@pc5-desktop:~$ sudo tail -f /var/log/lightdm/lightdm.log
[+41.96s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+41.96s] DEBUG: Session pid=721: Sending SIGTERM
[+41.99s] DEBUG: Greeter closed communication channel
[+41.99s] DEBUG: Session pid=721: Exited with return value 0
[+41.99s] DEBUG: Seat seat0: Session stopped
[+41.99s] DEBUG: Seat seat0: Greeter stopped, running session
[+41.99s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+42.01s] DEBUG: Session pid=1278: Running command /etc/X11/Xsession default
[+42.01s] DEBUG: Creating shared data directory /var/lib/lightdm/data/manfred
[+42.01s] DEBUG: Session pid=1278: Logging to .xsession-errors
[+301.44s] DEBUG: Activating VT 7
[+301.44s] DEBUG: Activating login1 session 4
[+301.45s] DEBUG: Seat seat0 changes active session to
[+301.45s] DEBUG: Seat seat0 changes active session to 4
[+301.45s] DEBUG: Session 4 is already active


[paxmark1]

Code marked up and lightdm log attached,  that helps a lot. 

I don't have xfce, I use sddm.  A quick check of the changelog of xfce 4.12, no major changes, just a lot of bug fixes.  Debian BTS for lightdm, nothing about lightdm getting hung up  at start.  A quick check of sddm and xfce4, no blogs or posts of people liking sddm  more than lightdm, just a few people with problems.   So my opinion it that it is not worthwhile  to change form lightdm to sddm to see if that cures.  I would say keep it with lightdm unless competent people say sddm has worked or cured promblems with XFCE4 for them..

You could check the Debian forums, but they discourage even Debian posting problems with testing.  Maybe watch on irc the XFCE channel and debian-xfce is there is one.  You can post on XFCE irc.  Pastebin your lightdm.log. 

Only other thing that comes to mind is do you have more than one DE that uses the same ~/home/blah     Sometimes the "dot files .config/   .local/     etc. can clash.   

peace out  mark

[seppalta]

I am having this problem, too, and am not using xfce4, but rather openbox:
$ sudo tail -f /var/log/lightdm/lightdm.log
[sudo] password for me:
[+36.15s] DEBUG: Seat seat0 changes active session to 2
[+36.15s] DEBUG: Session 2 is already active
[+791.34s] DEBUG: Session pid=1425: Terminated with signal 1
[+791.34s] DEBUG: Seat seat0: Session stopped
[+791.34s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+791.34s] DEBUG: Sending signal 15 to process 1215
[+791.35s] DEBUG: Got signal 15 from process 1
[+791.35s] DEBUG: Caught Terminated signal, shutting down
[+791.35s] DEBUG: Stopping display manager
[+791.35s] DEBUG: Seat seat0: Stopping

[seppalta]

Motivated by the previous discussion, I did some experimenting relative to display managers.  I noticed that I had both lightdm and slim installed with slim the default.  I tried every combination of installed, removed, defaulted, etc between these two display managers with the same result - a long delay (measured in minutes) after putting in user and password.  So I removed both slim and lightdm, and installed xdm.  Bingo!  Almost instant (like 2 or 3 seconds) desktop after login.  So I'm an xdm fan now.

[seppalta]

Upgrading to kernel 4.17 appears to have created chaos in login.  A second computer has experienced with lightdm and slim long (like 5 minutes) delay after log-in.  This time changing display manager to xdm resulted in a login screen staying up about 1 second, not long enough to type user name and password.  So I tried lxdm and all went well.  What's happening?

By the way, to install lxdm, use the "no-install-recommends" command to avoid getting an lxde desktop installed as well:

Code Select Expand

sudo apt-get install --no-install-recommends lxdm

[paxmark1]

Well if none of the "..." tried and true DM's are not working in XFCE4, I toss out this option.

Debian change logs

lxdm 2016 and a Feb 2018 minor update by non-maintainer

slim
april and may 2017

xdm
1 .11-2 1.11-3 Dec 2015
1.11-1   2011

Soo - if some brave soul wants to try out sddm in xfce that might be interesting.  sddm a clean write of a desktop manager made to not conflict with systemd (but has problems with wayland).  It is supposed to neutral to all desktop environments, not just a dm for kde (and some lxqt's) 

https://github.com/sddm/sddm
https://wiki.archlinux.org/index.php/SDDM#Long_load_time_before_SDDM_shows_the_greeter
https://metadata.ftp-master.debian.org/changelogs/main/s/sddm/sddm_0.18.0-1_changelog

peace out.

[pavroo]

The problem is not any session manager related itself.
Found a solution, simply run:

Code Select Expand

sudo apt purge libpam-gnome-keyring
sudo reboot
and let me know does it help, please.

[c.monty]

The problem is not any session manager related itself.
Found a solution, simply run:

Code Select Expand

sudo apt purge libpam-gnome-keyring
sudo reboot
and let me know does it help, please.

This solution solved my issue.

THX!!!

[hedon]

The problem is not any session manager related itself.
Found a solution, simply run:

Code Select Expand

sudo apt purge libpam-gnome-keyring
sudo reboot
and let me know does it help, please.

There is an extreme delay in the LXQt DE being displayed also.  However, I have Sparky LXQt in a VirtualBox VM, if that makes any difference.  The above commands have no effect in LXQt.  Is there an equivalent solution for Qt-based systems?

[pavroo]

Yes, try it running with Sparky kernel, works ok.

[paxmark1]

Sparky 5 = Deian testing. 
Debian 4.18 kernel in virtualbox comes up fast
i3 cpu, 8gb mem. 
libpam-gnome-keyring automatically installed on LXQT - has been for years.

Several year old lxqt install of sparky - debian kernel 4.18
atom cpu 1 gb memory, about a minute to spin up.
Never been a problem. 

As always I suggest looking for the slowdown via "systemd-analyze"  especially "systemd-analyze blame"  search forum and you will find more or look at digitalocean for systemd tutorials.     

For 3 year old lxqt  install that started in testing and is now in stable debian (backports enabled) it looks like

Code Select Expand

paxmark@raunes:~$ systemd-analyze blame
          5.627s connman-wait-online.service
          4.511s lvm2-monitor.service                                                                                                                                                       
          4.059s libvirtd.service                                                                                                                                                           
          3.713s apparmor.service                                                                                                                                                           
          2.886s dev-mapper-raunes\x2d\x2dvg\x2droot.device                                                                                                                                 
          1.853s gpm.service                                                                                                                                                                 
          1.773s systemd-journal-flush.service                                                                                                                                               
          1.760s networking.service                                                                                                                                                         
          1.442s lightdm.service                                                                                                                                                             
          1.437s keyboard-setup.service                                                                                                                                                     
          1.408s upower.service                                                                                                                                                             
          1.285s systemd-udevd.service                                                                                                                                                       
          1.273s systemd-fsck@dev-disk-by\x2duuid-4117\x2d423C.service                                                                                                                       
          1.198s user@1000.service                                                                                                                                                           
          1.144s lm-sensors.servi
and some more blah.

I confess, I do like lxqt, have for years.  peace out.