Arch Linux

thinman

Member

Registered: 2018-08-14

Posts: 13

[SOLVED]lightdm breaks on multiple PCs after 1:1.28.0-1 => 1:1.28.0-2

After a pacman -Syu on both my desktop and laptop, lightdm has failed to start after upgrading from 1:1.28.0-1 to 1:1.28.0-2.  Downgrading enables it to start again.  I haven't posted system specs as both machines are quite different so I don't think hardware would be the issue.  I'll post logs from the desktop.  I'm running XFCE on both as my DE.

journalctl -u lightdm.service

-- Reboot --
Feb 06 12:59:37 hp-elite systemd[1]: Starting Light Display Manager...
Feb 06 12:59:38 hp-elite lightdm[514]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Feb 06 12:59:38 hp-elite systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 06 12:59:38 hp-elite systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 06 12:59:38 hp-elite systemd[1]: Failed to start Light Display Manager.
Feb 06 12:59:38 hp-elite systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Feb 06 12:59:38 hp-elite systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Feb 06 12:59:38 hp-elite systemd[1]: Stopped Light Display Manager.
Feb 06 12:59:38 hp-elite systemd[1]: Starting Light Display Manager...
Feb 06 12:59:38 hp-elite lightdm[525]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesk>
Feb 06 12:59:38 hp-elite lightdm[525]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Feb 06 12:59:38 hp-elite systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 06 12:59:38 hp-elite systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 06 12:59:38 hp-elite systemd[1]: Failed to start Light Display Manager.
Feb 06 12:59:39 hp-elite systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Feb 06 12:59:39 hp-elite systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
Feb 06 12:59:39 hp-elite systemd[1]: Stopped Light Display Manager.
Feb 06 12:59:39 hp-elite systemd[1]: Starting Light Display Manager...
Feb 06 12:59:39 hp-elite lightdm[534]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesk>
Feb 06 12:59:39 hp-elite lightdm[534]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Feb 06 12:59:39 hp-elite systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 06 12:59:39 hp-elite systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 06 12:59:39 hp-elite systemd[1]: Failed to start Light Display Manager.
Feb 06 12:59:39 hp-elite systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Feb 06 12:59:39 hp-elite systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
Feb 06 12:59:39 hp-elite systemd[1]: Stopped Light Display Manager.
Feb 06 12:59:39 hp-elite systemd[1]: Starting Light Display Manager...
Feb 06 12:59:39 hp-elite lightdm[541]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesk>
Feb 06 12:59:39 hp-elite lightdm[541]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Feb 06 12:59:39 hp-elite systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 06 12:59:39 hp-elite systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 06 12:59:39 hp-elite systemd[1]: Failed to start Light Display Manager.
Feb 06 12:59:40 hp-elite systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Feb 06 12:59:40 hp-elite systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
Feb 06 12:59:40 hp-elite systemd[1]: Stopped Light Display Manager.
Feb 06 12:59:40 hp-elite systemd[1]: Starting Light Display Manager...
Feb 06 12:59:40 hp-elite lightdm[548]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesk>
Feb 06 12:59:40 hp-elite lightdm[548]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Feb 06 12:59:40 hp-elite systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 06 12:59:40 hp-elite systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 06 12:59:40 hp-elite systemd[1]: Failed to start Light Display Manager.
Feb 06 12:59:40 hp-elite systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Feb 06 12:59:40 hp-elite systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Feb 06 12:59:40 hp-elite systemd[1]: Stopped Light Display Manager.
Feb 06 12:59:40 hp-elite systemd[1]: lightdm.service: Start request repeated too quickly.
Feb 06 12:59:40 hp-elite systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 06 12:59:40 hp-elite systemd[1]: Failed to start Light Display Manager.

cat seat0-greeter.log

** Message: 13:04:18.603: Starting lightdm-gtk-greeter 2.0.6 (Sep 30 2018, 09:14:12)
** Message: 13:04:18.607: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf

** (lightdm-gtk-greeter:551): WARNING **: 13:04:18.820: [PIDs] Failed to execute command: /usr/lib/at-spi2-core/at-spi-bus-launcher

** (lightdm-gtk-greeter:551): WARNING **: 13:04:18.822: [PIDs] Failed to execute command: upstart

** (lightdm-gtk-greeter:551): WARNING **: 13:04:18.925: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files

(lightdm-gtk-greeter:551): Gtk-WARNING **: 13:04:18.957: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:551): Gtk-WARNING **: 13:04:22.674: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

cat lightdm.log
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.28.0, UID=0 PID=514
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+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: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.67s] DEBUG: Monitoring logind for seats
[+0.67s] DEBUG: New seat added from logind: seat0
[+0.67s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.67s] DEBUG: Seat seat0: Starting
[+0.67s] DEBUG: Seat seat0: Creating greeter session
[+0.68s] DEBUG: Seat seat0: Creating display server of type x
[+0.68s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.68s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.68s] DEBUG: Using VT 7
[+0.68s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.68s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.68s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.68s] DEBUG: XServer 0: Launching X Server
[+0.68s] DEBUG: Launching process 525: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.68s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.68s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.68s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.68s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.68s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.68s] DEBUG: User martin added
[+1.86s] DEBUG: Got signal 10 from process 525
[+1.86s] DEBUG: XServer 0: Got signal from X server :0
[+1.86s] DEBUG: XServer 0: Connecting to XServer :0
[+1.90s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 
[+1.90s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+1.90s] DEBUG: Session pid=541: Started with service 'lightdm-greeter', username 'lightdm'
[+1.92s] DEBUG: Session pid=541: Authentication complete with return value 0: Success
[+1.92s] DEBUG: Seat seat0: Session authenticated, running command
[+1.92s] DEBUG: Session pid=541: Running command /usr/bin/lightdm-gtk-greeter
[+1.92s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+1.92s] DEBUG: Session pid=541: Logging to /var/log/lightdm/seat0-greeter.log
[+2.00s] DEBUG: Activating VT 7
[+2.00s] DEBUG: Activating login1 session c1
[+2.00s] DEBUG: Seat seat0 changes active session to c1
[+2.00s] DEBUG: Session c1 is already active
[+2.27s] DEBUG: Greeter connected version=1.28.0 api=1 resettable=false
[+2.39s] DEBUG: Greeter start authentication for martin
[+2.39s] DEBUG: Session pid=596: Started with service 'lightdm', username 'martin'
[+2.40s] DEBUG: Session pid=596: Got 1 message(s) from PAM
[+2.40s] DEBUG: Prompt greeter with 1 message(s)
[+6.12s] DEBUG: Continue authentication
[+6.14s] DEBUG: Session pid=596: Authentication complete with return value 0: Success
[+6.14s] DEBUG: Authenticate result for user martin: Success
[+6.14s] DEBUG: User martin authorized
[+6.15s] DEBUG: Greeter requests session xfce
[+6.15s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+6.15s] DEBUG: Terminating login1 session c1
[+6.15s] DEBUG: Session pid=541: Sending SIGTERM
[+6.17s] DEBUG: Greeter closed communication channel
[+6.17s] DEBUG: Session pid=541: Exited with return value 0
[+6.17s] DEBUG: Seat seat0: Session stopped
[+6.17s] DEBUG: Seat seat0: Greeter stopped, running session
[+6.17s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+6.17s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 
[+6.17s] DEBUG: Session pid=596: Running command /etc/lightdm/Xsession startxfce4
[+6.17s] DEBUG: Creating shared data directory /var/lib/lightdm-data/martin
[+6.17s] DEBUG: Session pid=596: Logging to .xsession-errors
[+6.26s] DEBUG: Activating VT 7
[+6.26s] DEBUG: Activating login1 session 2
[+6.26s] DEBUG: Seat seat0 changes active session to 
[+6.26s] DEBUG: Seat seat0 changes active session to 2
[+6.26s] DEBUG: Session 2 is already active

Please let me know if any more logs or info are required and thanks for any help or advice.

Last edited by thinman (2019-02-06 20:18:44)

filotek

Member

Registered: 2018-08-15

Posts: 26

Re: [SOLVED]lightdm breaks on multiple PCs after 1:1.28.0-1 => 1:1.28.0-2

I had the exact same issue today... After upgrading lightdm from 1:1.28.0-1 to 1:1.28.0-2  and rebooting the system, the display manager failed to start after entering the password for the encrypted volume via Plymouth.

Only after I downgraded to 1:1.28.0-1 and rebooted again did everything start working normally.

# cat lightdm.log.old
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.28.0, UID=0 PID=1516
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+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: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.00s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.00s] DEBUG: Using VT 7
[+0.00s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.00s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.00s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.00s] DEBUG: XServer 0: Launching X Server
[+0.00s] DEBUG: Launching process 1522: /usr/bin/X -ardelay 200 -arinterval 25 :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.01s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.01s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.01s] DEBUG: User ffernand added

As with thinman, if there's anything more you need, just let me know.

spsf64

Member

From: FL, US or SP, BR

Registered: 2012-05-18

Posts: 109

Website

Re: [SOLVED]lightdm breaks on multiple PCs after 1:1.28.0-1 => 1:1.28.0-2

Bug already reported: https://bugs.archlinux.org/task/61654?p … ng=lightdm
Downgrade until new release seems to be the best option...

edit: 1:1.28.0-3 already available and fixes this issue!

Last edited by spsf64 (2019-02-06 19:02:47)

---

Sergio S.
Yes, I'm old and bald!

thinman

Member

Registered: 2018-08-14

Posts: 13

Re: [SOLVED]lightdm breaks on multiple PCs after 1:1.28.0-1 => 1:1.28.0-2

Thank you, marking as solved.