Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

lightdm is too slow to show login

Graphical Environments, Managers, Multimedia & Desktop questions.
Post Reply
Message
Author
alirezaimi
Posts: 144
Joined: 2011-01-12 16:25

lightdm is too slow to show login

#1 Post by alirezaimi »

Hi
the lightdm in my debian testing is too slow show login window when i turn my system on .

Code: Select all

root@alilap:/home/ali# cat /var/log/syslog | grep lightdm
Feb 22 23:03:41 alilap systemd[1]: Created slice User Slice of lightdm.
Feb 22 23:03:41 alilap systemd[1]: Started Session c1 of user lightdm.
Feb 22 23:03:41 alilap dbus-daemon[765]: [session uid=112 pid=765] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=112 pid=761 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:03:41 alilap at-spi-bus-launcher[766]: dbus-daemon[771]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=112 pid=761 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:03:41 alilap dbus-daemon[765]: [session uid=112 pid=765] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.5' (uid=112 pid=761 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:03:46 alilap systemd[1]: Removed slice User Slice of lightdm.
Feb 22 23:04:18 alilap dbus-daemon[516]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.59' (uid=1000 pid=1399 comm="/usr/bin/python3 /usr/bin/lightdm-gtk-greeter-sett")
Feb 22 23:04:30 alilap kernel: [   60.935475] lightdm-gtk-gre[1443]: segfault at 0 ip 00007f8cf38dbf89 sp 00007fff32271800 error 4 in libgtk-3.so.0.2200.26[7f8cf35f5000+6fa000]
Feb 22 23:04:44 alilap kernel: [   75.089773] lightdm-gtk-gre[1444]: segfault at 0 ip 00007f6cd8368f89 sp 00007ffc7b4cf4b0 error 4 in libgtk-3.so.0.2200.26[7f6cd8082000+6fa000]
Feb 22 23:04:46 alilap kernel: [   77.119122] lightdm-gtk-gre[1446]: segfault at 0 ip 00007f3cf5ecdf89 sp 00007ffff4d2a250 error 4 in libgtk-3.so.0.2200.26[7f3cf5be7000+6fa000]
Feb 22 23:04:53 alilap kernel: [   84.407267] lightdm-gtk-gre[1452]: segfault at 0 ip 00007fb576d8ef89 sp 00007fffbb9c67e0 error 4 in libgtk-3.so.0.2200.26[7fb576aa8000+6fa000]
Feb 22 23:05:09 alilap kernel: [  100.512143] lightdm-gtk-gre[1460]: segfault at 0 ip 00007fdd2872cf89 sp 00007fff0038b550 error 4 in libgtk-3.so.0.2200.26[7fdd28446000+6fa000]
Feb 22 23:05:19 alilap dbus-daemon[516]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.68' (uid=1000 pid=1466 comm="/usr/bin/python3 /usr/bin/lightdm-gtk-greeter-sett")
Feb 22 23:05:31 alilap kernel: [  121.567648] lightdm-gtk-gre[1483]: segfault at 0 ip 00007fb938b7bf89 sp 00007ffd71cabf30 error 4 in libgtk-3.so.0.2200.26[7fb938895000+6fa000]
Feb 22 23:06:42 alilap dbus-daemon[516]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.73' (uid=1000 pid=1868 comm="/usr/bin/python3 /usr/bin/lightdm-gtk-greeter-sett")
Feb 22 23:06:52 alilap kernel: [  202.636100] lightdm-gtk-gre[1884]: segfault at 0 ip 00007ffae7df8f89 sp 00007fff14734230 error 4 in libgtk-3.so.0.2200.26[7ffae7b12000+6fa000]
Feb 22 23:10:01 alilap dbus-daemon[516]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.75' (uid=1000 pid=2191 comm="/usr/bin/python3 /usr/bin/lightdm-gtk-greeter-sett")
Feb 22 23:10:18 alilap kernel: [  408.674835] lightdm-gtk-gre[2211]: segfault at 0 ip 00007fd5c3d8bf89 sp 00007ffd781836a0 error 4 in libgtk-3.so.0.2200.26[7fd5c3aa5000+6fa000]
Feb 22 23:11:01 alilap dbus-daemon[516]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.77' (uid=1000 pid=2238 comm="/usr/bin/python3 /usr/bin/lightdm-gtk-greeter-sett")
Feb 22 23:15:31 alilap systemd[1]: Created slice User Slice of lightdm.
Feb 22 23:15:31 alilap systemd[1]: Started Session c1 of user lightdm.
Feb 22 23:15:31 alilap dbus-daemon[797]: [session uid=112 pid=797] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=112 pid=793 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:15:31 alilap at-spi-bus-launcher[798]: dbus-daemon[803]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=112 pid=793 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:15:31 alilap dbus-daemon[797]: [session uid=112 pid=797] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.5' (uid=112 pid=793 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:15:37 alilap systemd[1]: Removed slice User Slice of lightdm.
Feb 22 23:26:25 alilap systemd[1]: Created slice User Slice of lightdm.
Feb 22 23:26:25 alilap systemd[1]: Started Session c1 of user lightdm.
Feb 22 23:26:25 alilap dbus-daemon[849]: [session uid=112 pid=849] Activating systemd to hand-off: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=112 pid=845 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:26:25 alilap at-spi-bus-launcher[850]: dbus-daemon[855]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=112 pid=845 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:26:25 alilap dbus-daemon[849]: [session uid=112 pid=849] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.5' (uid=112 pid=845 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:26:30 alilap systemd[1]: Removed slice User Slice of lightdm.
Feb 22 23:44:54 alilap systemd[1]: Created slice User Slice of lightdm.
Feb 22 23:44:54 alilap systemd[1]: Started Session c1 of user lightdm.
Feb 22 23:44:55 alilap dbus-daemon[849]: [session uid=112 pid=849] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=112 pid=845 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:44:55 alilap at-spi-bus-launcher[850]: dbus-daemon[855]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=112 pid=845 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:44:55 alilap dbus-daemon[849]: [session uid=112 pid=849] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.5' (uid=112 pid=845 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 22 23:45:00 alilap systemd[1]: Removed slice User Slice of lightdm.

Code: Select all

root@alilap:/home/ali# uname -a
Linux alilap 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64 GNU/Linux

Code: Select all

root@alilap:/home/ali# cat /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.18.3, UID=0 PID=660
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.06s] DEBUG: Monitoring logind for seats
[+0.06s] DEBUG: New seat added from logind: seat0
[+0.06s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.06s] DEBUG: Seat seat0: Starting
[+0.06s] DEBUG: Seat seat0: Creating greeter session
[+0.06s] DEBUG: Seat seat0: Creating display server of type x
[+0.07s] DEBUG: Seat seat0: Plymouth is running on VT 1, but this is less than the configured minimum of 7 so not replacing it
[+0.07s] DEBUG: Quitting Plymouth
[+0.09s] DEBUG: Using VT 7
[+0.09s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.09s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.09s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.09s] DEBUG: DisplayServer x-0: Launching X Server
[+0.09s] DEBUG: Launching process 692: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.09s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.09s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.09s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.10s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.10s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+47.23s] DEBUG: Got signal 10 from process 692
[+47.23s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+47.23s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+47.23s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+47.23s] DEBUG: Session pid=831: Started with service 'lightdm-greeter', username 'lightdm'
[+47.25s] DEBUG: Session pid=831: Authentication complete with return value 0: Success
[+47.25s] DEBUG: Seat seat0: Session authenticated, running command
[+47.25s] DEBUG: Session pid=831: Running command /usr/sbin/lightdm-gtk-greeter
[+47.25s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+47.25s] DEBUG: Session pid=831: Logging to /var/log/lightdm/seat0-greeter.log
[+47.36s] DEBUG: Activating VT 7
[+47.36s] DEBUG: Activating login1 session c1
[+47.36s] DEBUG: Seat seat0 changes active session to c1
[+47.36s] DEBUG: Session c1 is already active
[+47.67s] DEBUG: Greeter connected version=1.18.3 resettable=false
[+48.38s] DEBUG: Greeter start authentication
[+48.38s] DEBUG: Session pid=887: Started with service 'lightdm', username '(null)'
[+48.39s] DEBUG: Session pid=887: Got 1 message(s) from PAM
[+48.39s] DEBUG: Prompt greeter with 1 message(s)
[+50.74s] DEBUG: Greeter start authentication for ali
[+50.74s] DEBUG: Session pid=887: Sending SIGTERM
[+50.74s] DEBUG: Session pid=889: Started with service 'lightdm', username 'ali'
[+50.74s] DEBUG: Session pid=887: Terminated with signal 15
[+50.74s] DEBUG: Session: Failed during authentication
[+50.74s] DEBUG: Seat seat0: Session stopped
[+50.75s] DEBUG: Session pid=889: Got 1 message(s) from PAM
[+50.75s] DEBUG: Prompt greeter with 1 message(s)
[+52.70s] DEBUG: Continue authentication
[+52.72s] DEBUG: Session pid=889: Authentication complete with return value 0: Success
[+52.72s] DEBUG: Authenticate result for user ali: Success
[+52.72s] DEBUG: User ali authorized
[+52.74s] DEBUG: Greeter sets language en_US.utf8
[+52.76s] DEBUG: Greeter requests session cinnamon
[+52.76s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+52.76s] DEBUG: Session pid=831: Sending SIGTERM
[+52.79s] DEBUG: Greeter closed communication channel
[+52.79s] DEBUG: Session pid=831: Exited with return value 0
[+52.79s] DEBUG: Seat seat0: Session stopped
[+52.79s] DEBUG: Seat seat0: Greeter stopped, running session
[+52.79s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+52.79s] DEBUG: Session pid=889: Running command /etc/X11/Xsession cinnamon-session-cinnamon
[+52.79s] DEBUG: Creating shared data directory /var/lib/lightdm/data/ali
[+52.79s] DEBUG: Session pid=889: Logging to .xsession-errors
[+52.90s] DEBUG: Activating VT 7
[+52.90s] DEBUG: Activating login1 session 2
[+52.90s] DEBUG: Seat seat0 changes active session to 
[+52.90s] DEBUG: Seat seat0 changes active session to 2
[+52.90s] DEBUG: Session 2 is already active

Bulkley
Posts: 6383
Joined: 2006-02-11 18:35
Has thanked: 2 times
Been thanked: 39 times

Re: lightdm is too slow to show login

#2 Post by Bulkley »

Try Slim.

I think all DMs are too slow, too awkward and unnecessary. That's the nature of the beast. I prefer to boot to a command prompt, enter my username and password and then startx which I have shortened to sx.

alirezaimi
Posts: 144
Joined: 2011-01-12 16:25

Re: lightdm is too slow to show login

#3 Post by alirezaimi »

Bulkley wrote:Try Slim.

I think all DMs are too slow, too awkward and unnecessary. That's the nature of the beast. I prefer to boot to a command prompt, enter my username and password and then startx which I have shortened to sx.
Thanks for your response,
I install slim and just like lightdm, slim was too slow !
I think in debian this is a natural thing that visual effect and desktop experience is a little down side !

User avatar
bw123
Posts: 4015
Joined: 2011-05-09 06:02
Has thanked: 1 time
Been thanked: 28 times

Re: lightdm is too slow to show login

#4 Post by bw123 »

alirezaimi wrote:

[+0.10s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+47.23s] DEBUG: Got signal 10 from process 692

I install slim and just like lightdm, slim was too slow !
I think in debian this is a natural thing that visual effect and desktop experience is a little down side !
Yeah that is too long, you got segfaults in your syslog too. If you are getting segfault with a lot of things, run a memtest for awhile. If you installed with that happening and it's bad ram, then I would guess just about anything or everything could be corrupted.

Maybe you should use stable? here's a sample what i get from the same part of lightdm.log it loads up the greeter pretty darn snappy.

[+0.17s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+1.41s] DEBUG: Got signal 10 from process 1549
resigned by AI ChatGPT

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: lightdm is too slow to show login

#5 Post by Head_on_a_Stick »

Bulkley wrote:I prefer to boot to a command prompt, enter my username and password and then startx which I have shortened to sx.
Add this line to the end of ~/.profile to automatically start your desktop after a TTY1 login:

Code: Select all

[ "$(tty)" = "/dev/tty1" ] && exec startx
deadbang

User avatar
None1975
df -h | participant
df -h | participant
Posts: 1388
Joined: 2015-11-29 18:23
Location: Russia, Kaliningrad
Has thanked: 45 times
Been thanked: 65 times

Re: lightdm is too slow to show login

#6 Post by None1975 »

Why do you use that animal-lightdm? It's much easier and easier to remove it and use startx command...
OS: Debian 12.4 Bookworm / DE: Enlightenment
Debian Wiki | DontBreakDebian, My config files on github

Bulkley
Posts: 6383
Joined: 2006-02-11 18:35
Has thanked: 2 times
Been thanked: 39 times

Re: lightdm is too slow to show login

#7 Post by Bulkley »

alirezaimi, are you running your own kernel? If so, have you tried the Debian kernel as a comparison?

Are you running a mixed system? What's in your sources.list?

As bw123, suggested, you would probably get better results with Stable.

Post Reply