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 loads twice

Graphical Environments, Managers, Multimedia & Desktop questions.
Post Reply
Message
Author
ojensen5115
Posts: 2
Joined: 2016-03-06 17:03

Lightdm loads twice

#1 Post by ojensen5115 »

I have an odd issue -- fairly fresh Debian Testing install, using Lightdm.

After booting up, Lightdm starts, and then a moment or two later restarts. As a result, any keystrokes captured by the first run (e.g. the first few characters of my username) are lost. My lightdm log is:

Code: Select all

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.16.7, UID=0 PID=827
[+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:   [SeatDefaults] is now called [Seat:*], please update this configuration
[+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.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.02s] DEBUG: Seat seat0: Plymouth is running on VT 1, but this is less than the configured minimum of 7 so not replacing it
[+0.02s] DEBUG: Quitting Plymouth
[+0.08s] DEBUG: Using VT 7
[+0.08s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.08s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.08s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.08s] DEBUG: DisplayServer x-0: Launching X Server
[+0.08s] DEBUG: Launching process 941: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.08s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.08s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.08s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.08s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.08s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.63s] DEBUG: Got signal 10 from process 941
[+0.63s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+0.63s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+0.63s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.63s] DEBUG: Session pid=1328: Started with service 'lightdm-greeter', username 'lightdm'
[+0.65s] DEBUG: Session pid=1328: Authentication complete with return value 0: Success
[+0.65s] DEBUG: Seat seat0: Session authenticated, running command
[+0.65s] DEBUG: Session pid=1328: Running command /usr/sbin/lightdm-gtk-greeter
[+0.65s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+0.65s] DEBUG: Session pid=1328: Logging to /var/log/lightdm/x-0-greeter.log
[+0.72s] DEBUG: Activating VT 7
[+0.72s] DEBUG: Activating login1 session c1
[+0.72s] DEBUG: Seat seat0 changes active session to c1
[+0.72s] DEBUG: Session c1 is already active
[+0.87s] DEBUG: Session pid=1328: Greeter connected version=1.16.7 resettable=false
[+1.20s] DEBUG: Session pid=1328: Greeter start authentication
[+1.20s] DEBUG: Session pid=1357: Started with service 'lightdm', username '(null)'
[+1.20s] DEBUG: Session pid=1357: Got 1 message(s) from PAM
[+1.20s] DEBUG: Session pid=1328: Prompt greeter with 1 message(s)
[+3.84s] DEBUG: Session pid=1328: Greeter start authentication for ojensen
[+3.84s] DEBUG: Session pid=1357: Sending SIGTERM
[+3.84s] DEBUG: Session pid=1369: Started with service 'lightdm', username 'ojensen'
[+3.84s] DEBUG: Session pid=1357: Terminated with signal 15
[+3.84s] DEBUG: Session: Failed during authentication
[+3.84s] DEBUG: Seat seat0: Session stopped
[+3.85s] DEBUG: Session pid=1369: Got 1 message(s) from PAM
[+3.85s] DEBUG: Session pid=1328: Prompt greeter with 1 message(s)
[+5.31s] DEBUG: Session pid=1328: Continue authentication
[+5.32s] DEBUG: Session pid=1369: Authentication complete with return value 0: Success
[+5.32s] DEBUG: Session pid=1328: Authenticate result for user ojensen: Success
[+5.32s] DEBUG: Session pid=1328: User ojensen authorized
[+5.34s] DEBUG: Session pid=1328: Greeter sets language en_US.utf8
[+5.42s] DEBUG: Session pid=1328: Greeter requests session lightdm-xsession
[+5.43s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+5.43s] DEBUG: Session pid=1328: Sending SIGTERM
[+5.45s] DEBUG: Session pid=1328: Greeter closed communication channel
[+5.45s] DEBUG: Session pid=1328: Exited with return value 0
[+5.45s] DEBUG: Seat seat0: Session stopped
[+5.45s] DEBUG: Seat seat0: Greeter stopped, running session
[+5.45s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+5.45s] DEBUG: Session pid=1369: Running command /etc/X11/Xsession default
[+5.45s] DEBUG: Creating shared data directory /var/lib/lightdm/data/ojensen
[+5.45s] DEBUG: Session pid=1369: Logging to .xsession-errors
[+5.51s] DEBUG: Activating VT 7
[+5.51s] DEBUG: Activating login1 session 1
[+5.51s] DEBUG: Seat seat0 changes active session to 1
[+5.51s] DEBUG: Session 1 is already active
This log shows me seeing the login screen, waiting for it to restart, and then logging in correctly on the first attempt.

The problem seems pretty similar to the one described here, except that the fix found at the end does not seem to apply in this case. Any help would be much appreciated, as while the effects of this issue are benign, it's fairly annoying. Thank you for your time.

Post Reply