You are not logged in.

#1 2016-04-12 03:32:51

Thorned_Rose
Member
From: New Zealand
Registered: 2015-12-30
Posts: 40

[RESOLVED] LightDM fails to start after system upgrade

LightDM was working fine up until I did a system upgrade a few days ago (in which lightdm-webkit2-greeter had issues).

When I tried to do an system upgrade, Pacman came up with the error:

looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: lightdm-webkit2-greeter: installing webkit2gtk (2.12.0-2) breaks dependency 'webkit2gtk<2.12'
:: lightdm-webkit2-greeter: installing gtk3 (3.20.2-1) breaks dependency 'gtk3<3.20'

See here for more info:
https://forum.antergos.com/topic/4263/i … t2-greeter
https://github.com/Antergos/antergos-packages/issues/94

I made the stupid mistake of temporarily uninstalling lightdm-webkit2-greeter to upgrade everything else. Since the webkit2 greeter was broken because of the GTK updates, I switched to using SDDM until the webkit2 greeter was updated.

Once the webkit2 greeter was updated and it was confirmed to now be working, I installed it again, disabled SDDM and enabled LightDM again.

However, when I did tried to start the lightdm.service, I got this error:

Job for lightdm.service failed because the control process exited with error code. See "systemctl status lightdm.service" and "journalctl -xe" for details.

I tried completely removing LightDM, all it's greeters and themes, deleting the config files and reinstalling (LightDM and lightdm-gtk-greeter) and editing the lightdm config file appropriately (left as default except to change the greeter to lightdm-gtk-greeter).

No difference, exactly the same errors.

In between I also switched to the Deepin DE (from Openbox although I still have Openbox installed) and installed the Deepin greeter (again editing config file to change the greeter). No difference. Interestingly, Deepin's lock screen works just fine.

Here's the log files:

Lightdm.log

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.18.1, UID=0 PID=1765
[+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: 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.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to /run/lightdm/root/:0
[+0.01s] DEBUG: DisplayServer x-0: Launching X Server
[+0.01s] DEBUG: Launching process 1772: /usr/sbin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: DisplayServer x-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] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.01s] DEBUG: Process 1772 exited with return value 1
[+0.01s] DEBUG: DisplayServer x-0: X server stopped
[+0.01s] DEBUG: Releasing VT 7
[+0.02s] DEBUG: DisplayServer x-0: Removing X server authority /run/lightdm/root/:0
[+0.02s] DEBUG: Seat seat0: Display server stopped
[+0.02s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+0.02s] DEBUG: Seat seat0: Stopping
[+0.02s] DEBUG: Seat seat0: Stopping session
[+0.02s] DEBUG: Seat seat0: Session stopped
[+0.02s] DEBUG: Seat seat0: Stopped
[+0.02s] DEBUG: Required seat has stopped
[+0.02s] DEBUG: Stopping display manager
[+0.02s] DEBUG: Display manager stopped
[+0.02s] DEBUG: Stopping daemon
[+0.02s] DEBUG: Seat seat0: Stopping session

journalctl:

[rose@visas-marr ~]$ journalctl -u lightdm.service | grep "Apr 12"
Apr 12 10:57:31 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 10:57:31 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 10:57:31 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 10:57:31 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 10:57:31 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 10:57:31 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 10:57:31 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 10:57:31 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 10:57:31 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 10:57:31 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 10:57:31 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 10:57:31 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 10:57:31 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 10:57:31 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 10:57:31 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 10:57:32 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 10:57:32 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 10:57:32 visas-marr systemd[1]: lightdm.service: Start request repeated too quickly.
Apr 12 10:57:32 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 11:04:48 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 11:04:49 visas-marr lightdm[1721]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 11:04:49 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 11:04:49 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 11:04:49 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 11:04:49 visas-marr lightdm[1731]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 11:04:49 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 11:04:49 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 11:04:49 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 11:04:49 visas-marr lightdm[1746]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 11:04:49 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 11:04:49 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 11:04:50 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 11:04:50 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 11:04:50 visas-marr lightdm[1756]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 11:04:50 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 11:04:50 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 11:04:50 visas-marr systemd[1]: Starting Light Display Manager...
Apr 12 11:04:50 visas-marr lightdm[1765]: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 11:04:50 visas-marr systemd[1]: Failed to start Light Display Manager.
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 12 11:04:50 visas-marr systemd[1]: Stopped Light Display Manager.
Apr 12 11:04:50 visas-marr systemd[1]: lightdm.service: Start request repeated too quickly.
Apr 12 11:04:50 visas-marr systemd[1]: Failed to start Light Display Manager.

lightdm.conf: http://pastebin.com/JDz5rPtn

An internet search of "Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?" comes up with next to nothing or nothing that I can see as helpful anyway.
Help much appreciated smile

Last edited by Thorned_Rose (2016-04-18 01:24:35)

Offline

#2 2016-04-12 05:05:31

loafer
Member
From: the pub
Registered: 2009-04-14
Posts: 1,772

Re: [RESOLVED] LightDM fails to start after system upgrade

Are you using Arch or Antergos?


All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.

Offline

#3 2016-04-12 06:59:04

Thorned_Rose
Member
From: New Zealand
Registered: 2015-12-30
Posts: 40

Re: [RESOLVED] LightDM fails to start after system upgrade

I'm using Arch.

 rose@visas-marr
 OS: Arch Linux 
 Kernel: x86_64 Linux 4.4.5-1-ARCH
 Uptime: 9m
 Packages: 1229
 Shell: bash 4.3.42
 Resolution: 1920x1200
 WM: Mutter(DeepinGala)
 WM Theme: Adwaita
 Icon Theme: deepin
 Font: DejaVu Sans 10
 CPU: Intel Core2 Quad CPU Q6600 @ 2.4GHz
 GPU: GeForce GTX 650 Ti
 RAM: 1385MiB / 6979MiB

(The Antergos links are because the webkit2 greeter is maintained by the Antergos team)

Offline

#4 2016-04-13 22:51:09

Thorned_Rose
Member
From: New Zealand
Registered: 2015-12-30
Posts: 40

Re: [RESOLVED] LightDM fails to start after system upgrade

After the latest rounds of updates, still having this problem. Was hopeful that something weird was going on in a distantly related package but no dice. Still getting this error:

Job for lightdm.service failed because the control process exited with error code. See "systemctl status lightdm.service" and "journalctl -xe" for details.

with the same errors in the log files in my first post.

Offline

#5 2016-04-14 00:19:30

Thorned_Rose
Member
From: New Zealand
Registered: 2015-12-30
Posts: 40

Re: [RESOLVED] LightDM fails to start after system upgrade

Xorg.0.log:

[  3082.682] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
[  3082.682] _XSERVTransMakeAllCOTSServerListeners: server already running
[  3082.682] (EE) 
Fatal server error:
[  3082.682] (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) 
[  3082.682] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[  3082.682] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  3082.682] (EE) 
[  3082.682] (EE) Server terminated with error (1). Closing log file.

Offline

#6 2016-04-14 11:21:40

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: [RESOLVED] LightDM fails to start after system upgrade

What does

journalctl -xe

tell you? The error message indicated you should look there first.


Matt

"It is very difficult to educate the educated."

Offline

#7 2016-04-14 21:51:35

Thorned_Rose
Member
From: New Zealand
Registered: 2015-12-30
Posts: 40

Re: [RESOLVED] LightDM fails to start after system upgrade

mrunion wrote:

What does

journalctl -xe

tell you? The error message indicated you should look there first.

Apr 15 09:48:33 visas-marr lightdm[26700]: Failed to use bus name org.freedesktop.DisplayManager, do you hav
Apr 15 09:48:33 visas-marr systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 15 09:48:33 visas-marr systemd[1]: Failed to start Light Display Manager.
-- Subject: Unit lightdm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit lightdm.service has failed.
-- 
-- The result is failed.
Apr 15 09:48:33 visas-marr systemd[1]: lightdm.service: Unit entered failed state.
Apr 15 09:48:33 visas-marr systemd[1]: lightdm.service: Failed with result 'exit-code'.
Apr 15 09:48:33 visas-marr systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Apr 15 09:48:33 visas-marr systemd[1]: Stopped Light Display Manager.
-- Subject: Unit lightdm.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit lightdm.service has finished shutting down.
Apr 15 09:48:33 visas-marr systemd[1]: lightdm.service: Start request repeated too quickly.
Apr 15 09:48:33 visas-marr systemd[1]: Failed to start Light Display Manager.
-- Subject: Unit lightdm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit lightdm.service has failed.
-- 
-- The result is failed.

Same error as in my first post sad

Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?

Offline

#8 2016-04-18 01:23:59

Thorned_Rose
Member
From: New Zealand
Registered: 2015-12-30
Posts: 40

Re: [RESOLVED] LightDM fails to start after system upgrade

After the next round of updates in which the Nvidia drivers (v364.16-2) and the kernel (4.5-1) were upgraded, the issue seemingly resolved itself. I have no idea exactly what fixed it. I do recall seeing a thread somewhere about Nvidia drivers causing problems with LightDM and that for them rolling back the drivers resolved their problem. So possibly it was a video driver issue.

I'll mark this as resolved as opposed to solved given I never actually worked out what the problem was and fixed it.

Offline

Board footer

Powered by FluxBB