Arch Linux

k4li

Member

From: Ljubljana

Registered: 2016-04-16

Posts: 25

[SOLVED] Lightdm won't start on boot

Hi,

my lightdm won't start on boot after driver update(not shure if that is conected):
log:

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.18.2, UID=0 PID=618
[+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.02s] DEBUG: Launching process 625: /usr/sbin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.02s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] 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.10s] DEBUG: Seat seat0 changes active session to 
[+0.10s] CRITICAL: session_get_login1_session_id: assertion 'session != NULL' failed
[+0.69s] DEBUG: Got signal 10 from process 625
[+0.69s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+0.69s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+0.69s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.69s] DEBUG: Session pid=637: Started with service 'lightdm-greeter', username 'lightdm'
[+0.70s] DEBUG: Session pid=637: Authentication complete with return value 0: Success
[+0.70s] DEBUG: Seat seat0: Session authenticated, running command
[+0.70s] DEBUG: Session pid=637: Running command /usr/sbin/lightdm-gtk-greeter
[+0.70s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.70s] DEBUG: Session pid=637: Logging to /var/log/lightdm/seat0-greeter.log
[+0.75s] DEBUG: Activating VT 7
[+0.75s] DEBUG: Activating login1 session c2
[+1.07s] DEBUG: Greeter connected version=1.18.2 resettable=false
[+1.34s] DEBUG: Greeter start authentication for k4li
[+1.35s] DEBUG: Session pid=675: Started with service 'lightdm', username 'k4li'
[+1.35s] DEBUG: Session pid=675: Got 1 message(s) from PAM
[+1.35s] DEBUG: Prompt greeter with 1 message(s)
[+5.87s] DEBUG: Continue authentication
[+5.88s] DEBUG: Session pid=675: Authentication complete with return value 0: Success
[+5.88s] DEBUG: Authenticate result for user k4li: Success
[+5.88s] DEBUG: User k4li authorized
[+5.88s] DEBUG: Greeter sets language en_US.utf8
[+5.92s] DEBUG: Greeter requests session xfce
[+5.92s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+5.92s] DEBUG: Session pid=637: Sending SIGTERM
[+5.96s] DEBUG: Greeter closed communication channel
[+5.96s] DEBUG: Session pid=637: Exited with return value 0
[+5.96s] DEBUG: Seat seat0: Session stopped
[+5.96s] DEBUG: Seat seat0: Greeter stopped, running session
[+5.96s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+5.96s] DEBUG: Session pid=675: Running command /etc/lightdm/Xsession startxfce4
[+5.96s] DEBUG: Creating shared data directory /var/lib/lightdm-data/k4li
[+5.96s] DEBUG: Session pid=675: Logging to .xsession-errors
[+5.99s] DEBUG: Activating VT 7
[+5.99s] DEBUG: Activating login1 session c3
[+5.99s] DEBUG: Seat seat0 changes active session to 

How do I fix this?

Last edited by k4li (2016-08-15 08:08:09)

BlahBlahBlase

Member

From: Tucson, AZ

Registered: 2015-09-15

Posts: 35

Re: [SOLVED] Lightdm won't start on boot

Is the systemd service still enabled?

Last edited by BlahBlahBlase (2016-08-09 13:14:22)

---

"Full disclosure, I'm drunk right now. And if you can't handle that, you can't handle science."

k4li

Member

From: Ljubljana

Registered: 2016-04-16

Posts: 25

Re: [SOLVED] Lightdm won't start on boot

Yes, I have lightdm service enabled but It crashes at boot.

dockland

Member

From: Sweden

Registered: 2015-06-06

Posts: 861

Re: [SOLVED] Lightdm won't start on boot

Please show us the output of your /etc/lightdm/lightdm.conf

---

I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

k4li

Member

From: Ljubljana

Registered: 2016-04-16

Posts: 25

Re: [SOLVED] Lightdm won't start on boot

here it is:

#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# logind-check-graphical = True to on start seats that are marked as graphical by logind
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
# backup-logs = True to move add a .old suffix to old log files when opening new ones
#
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7 # Setting this to a value < 7 implies security issues, see FS#46799
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#logind-check-graphical=false
#log-directory=/var/log/lightdm
run-directory=/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=/usr/share/lightdm/greeters:/usr/share/xgreeters
#backup-logs=true

#
# Seat configuration
#
# Seat configuration is matched against the seat name glob in the section, for example:
# [Seat:*] matches all seats and is applied first.
# [Seat:seat0] matches the seat named "seat0".
# [Seat:seat-thin-client*] matches all seats that have names that start with "seat-thin-client".
#
# type = Seat type (xlocal, xremote, unity)
# pam-service = PAM service to use for login
# pam-autologin-service = PAM service to use for autologin
# pam-greeter-service = PAM service to use for greeters
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xmir-command = Xmir server command to run (can also contain arguments e.g. Xmir -special-option)
# xserver-config = Config file to pass to X server
# xserver-layout = Layout to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# unity-compositor-command = Unity compositor command to run (can also contain arguments e.g. unity-system-compositor -special-option)
# unity-compositor-timeout = Number of seconds to wait for compositor to start
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-user-switching = True if allowed to switch users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# display-stopped-script = Script to run after stopping the display server (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
# autologin-user = User to log in with by default (overrides autologin-guest)
# autologin-user-timeout = Number of seconds to wait before loading default user
# autologin-session = Session to load for automatic login (overrides user-session)
# autologin-in-background = True if autologin session should not be immediately activated
# exit-on-failure = True if the daemon should exit if this seat fails
#
[Seat:*]
#type=xlocal
#pam-service=lightdm
#pam-autologin-service=lightdm-autologin
#pam-greeter-service=lightdm-greeter
#xserver-command=X
#xmir-command=Xmir
#xserver-config=
#xserver-layout=
#xserver-allow-tcp=false
#xserver-share=true
#xserver-hostname=
#xserver-display-number=
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
#unity-compositor-command=unity-system-compositor
#unity-compositor-timeout=60
#greeter-session=example-gtk-gnome
#greeter-hide-users=false
#greeter-allow-guest=true
#greeter-show-manual-login=false
#greeter-show-remote-login=true
#user-session=default
#allow-user-switching=true
#allow-guest=true
#guest-session=
session-wrapper=/etc/lightdm/Xsession
#greeter-wrapper=
#guest-wrapper=
#display-setup-script=
#display-stopped-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=
#autologin-guest=false
#autologin-user=
#autologin-user-timeout=0
#autologin-in-background=false
#autologin-session=
#exit-on-failure=false

#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# listen-address = Host/address to listen for XDMCP connections (use all addresses if not present)
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
# hostname = Hostname to report to XDMCP clients (defaults to system hostname if unset)
#
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn.  Alternatively
# it can be a word and the first 7 characters are used as the key.
#
[XDMCPServer]
#enabled=false
#port=177
#listen-address=
#key=
#hostname=

#
# VNC Server configuration
#
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# listen-address = Host/address to listen for VNC connections (use all addresses if not present)
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
#
[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#listen-address=
#width=1024
#height=768
#depth=8


   [LightDM]
   logind-check-graphical=true

dockland

Member

From: Sweden

Registered: 2015-06-06

Posts: 861

Re: [SOLVED] Lightdm won't start on boot

Unmark #greeter-session=example-gtk-gnome and name it after your greeter. eg
greeter-session=your greeter here

---

I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

k4li

Member

From: Ljubljana

Registered: 2016-04-16

Posts: 25

Re: [SOLVED] Lightdm won't start on boot

Unmark #greeter-session=example-gtk-gnome and name it after your greeter. eg
greeter-session=your greeter here

This doesn't work for me.

dockland

Member

From: Sweden

Registered: 2015-06-06

Posts: 861

Re: [SOLVED] Lightdm won't start on boot

What greeter do you use?

---

I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

loqs

Member

Registered: 2014-03-06

Posts: 17,321

Re: [SOLVED] Lightdm won't start on boot

The lightdm.log seems to be for a successful session through to starting xfce4.  So it might be that the failure occurs before any new log is generated.
What is the output of

journalctl -b -u lightdm.service

and

systemctl status lightdm.service

k4li

Member

From: Ljubljana

Registered: 2016-04-16

Posts: 25

Re: [SOLVED] Lightdm won't start on boot

journalctl -b -u lightdm.service:

-- Logs begin at Tue 2016-06-28 13:33:38 UTC, end at Sun 2016-08-14 11:05:23 UTC
Aug 13 19:17:27 madison systemd[1]: Starting Light Display Manager...
Aug 13 19:17:27 madison systemd[1]: Started Light Display Manager.
Aug 13 19:17:27 madison lightdm[597]: ** (lightdm:597): CRITICAL **: session_get
Aug 13 19:17:28 madison lightdm[622]: pam_unix(lightdm-greeter:session): session
Aug 13 19:17:32 madison lightdm[659]: pam_unix(lightdm:session): session opened 
Aug 14 10:26:13 madison lightdm[4400]: pam_unix(lightdm-greeter:session): sessio

systemctl status lightdm.service:

-- Logs begin at Tue 2016-06-28 13:33:38 UTC, end at Sun 2016-08-14 11:05:23 UTC
Aug 13 19:17:27 madison systemd[1]: Starting Light Display Manager...
Aug 13 19:17:27 madison systemd[1]: Started Light Display Manager.
Aug 13 19:17:27 madison lightdm[597]: ** (lightdm:597): CRITICAL **: session_get
Aug 13 19:17:28 madison lightdm[622]: pam_unix(lightdm-greeter:session): session
Aug 13 19:17:32 madison lightdm[659]: pam_unix(lightdm:session): session opened 
Aug 14 10:26:13 madison lightdm[4400]: pam_unix(lightdm-greeter:session): sessio
[k4li@madison ~]$ systemctl status lightdm.service
● lightdm.service - Light Display Manager
   Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor pres
   Active: active (running) since Sat 2016-08-13 19:17:27 UTC; 15h ago
     Docs: man:lightdm(1)
 Main PID: 597 (lightdm)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/lightdm.service
           ├─597 /usr/bin/lightdm
           └─603 /usr/lib/xorg-server/Xorg :0 -seat seat0 -auth /run/lightdm/roo

Aug 13 19:17:27 madison systemd[1]: Starting Light Display Manager...
Aug 13 19:17:27 madison systemd[1]: Started Light Display Manager.
Aug 13 19:17:27 madison lightdm[597]: ** (lightdm:597): CRITICAL **: session_get
Aug 13 19:17:28 madison lightdm[622]: pam_unix(lightdm-greeter:session): session
Aug 13 19:17:32 madison lightdm[659]: pam_unix(lightdm:session): session opened 
Aug 14 10:26:13 madison lightdm[4400]: pam_unix(lightdm-greeter:session): sessio

How ever I can start lightdm manualy.

loqs

Member

Registered: 2014-03-06

Posts: 17,321

Re: [SOLVED] Lightdm won't start on boot

The output of the following please

$ systemctl list-unit-files | grep enabled

$ systemctl get-default

$ systemctl list-dependencies --reverse lightdm.service

dockland

Member

From: Sweden

Registered: 2015-06-06

Posts: 861

Re: [SOLVED] Lightdm won't start on boot

You are calling for lightdm-gtk-greeter but is lightdm-gtk-greeter stated in greeter session?

like: greeter-session=lightdm-gtk-greeter

---

I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

loqs

Member

Registered: 2014-03-06

Posts: 17,321

Re: [SOLVED] Lightdm won't start on boot

How ever I can start lightdm manualy.

How do you start lightdm manually?
Once it is started does it function correctly?

k4li

Member

From: Ljubljana

Registered: 2016-04-16

Posts: 25

Re: [SOLVED] Lightdm won't start on boot

How ever I can start lightdm manualy.

How do you start lightdm manually?
Once it is started does it function correctly?

I have to run

 sudo systemctl start lightdm 

and it does run normaly, it even starts when I wake up from suspend.

loqs

Member

Registered: 2014-03-06

Posts: 17,321

Re: [SOLVED] Lightdm won't start on boot

The output requested in post #11 please plus the output of

$ systemctl status display-manager.service

k4li

Member

From: Ljubljana

Registered: 2016-04-16

Posts: 25

Re: [SOLVED] Lightdm won't start on boot

● lightdm.service - Light Display Manager
   Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor pres
   Active: active (running) since Sun 2016-08-14 16:20:07 UTC; 1min 27s ago
     Docs: man:lightdm(1)
 Main PID: 588 (lightdm)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/lightdm.service
           ├─588 /usr/bin/lightdm
           └─594 /usr/lib/xorg-server/Xorg :0 -seat seat0 -auth /run/lightdm/roo

Aug 14 16:20:07 madison systemd[1]: Starting Light Display Manager...
Aug 14 16:20:07 madison systemd[1]: Started Light Display Manager.
Aug 14 16:20:07 madison lightdm[588]: ** (lightdm:588): CRITICAL **: session_get
Aug 14 16:20:08 madison lightdm[614]: pam_unix(lightdm-greeter:session): session
Aug 14 16:20:21 madison lightdm[651]: pam_unix(lightdm:session): session opened 
lines 1-15/15 (END)...skipping...
● lightdm.service - Light Display Manager
   Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2016-08-14 16:20:07 UTC; 1min 27s ago
     Docs: man:lightdm(1)
 Main PID: 588 (lightdm)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/lightdm.service
           ├─588 /usr/bin/lightdm
           └─594 /usr/lib/xorg-server/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

Aug 14 16:20:07 madison systemd[1]: Starting Light Display Manager...
Aug 14 16:20:07 madison systemd[1]: Started Light Display Manager.
Aug 14 16:20:07 madison lightdm[588]: ** (lightdm:588): CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed
Aug 14 16:20:08 madison lightdm[614]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Aug 14 16:20:21 madison lightdm[651]: pam_unix(lightdm:session): session opened for user k4li by (uid=0)

Last edited by k4li (2016-08-14 14:23:41)

loqs

Member

Registered: 2014-03-06

Posts: 17,321

Re: [SOLVED] Lightdm won't start on boot

The output requested in post #11 please

Also please include the command that generated the output and some of the output from systemctl / journalctl is being truncated the options "--no-pager  -l" may help
Edit:

Aug 14 16:20:07 madison lightdm[588]: ** (lightdm:588): CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed

It could well be that I am on the wrong path everything so far seems to indicate it should launch properly at startup although because you then manually start the service it makes some of the output harder to interpret.
There are lots of other threads relating to the above error message that have gone without resolution ( save for system reinstall ) with no explanation of why that succeeded.
Edit2:
Example of the confusion the "journalctl -b -u lightdm.service" output which should log every start of the service for one boot shows one start.
If that was caused by "sudo systemctl start lightdm" then it means systemd did not attempt to start the service even though it is enabled.
If that one start is the automatic start on boot then why are there no records of service failure, the automatic restart that should follow or the manual activation that was needed due to the failure.

Last edited by loqs (2016-08-14 17:22:40)

k4li

Member

From: Ljubljana

Registered: 2016-04-16

Posts: 25

Re: [SOLVED] Lightdm won't start on boot

systemctl list-unit-files | grep enabled :

autovt@.service                                                        enabled  
dbus-org.freedesktop.NetworkManager.service                            enabled  
dbus-org.freedesktop.nm-dispatcher.service                             enabled  
dhcpcd@.service                                                        enabled  
display-manager.service                                                enabled  
getty@.service                                                         enabled  
lightdm.service                                                        enabled  
NetworkManager-dispatcher.service                                      enabled  
NetworkManager.service                                                 enabled  
nmbd.service                                                           enabled  
smbd.service                                                           enabled  
sshd.service                                                           enabled  
default.target                                                         enabled  
multi-user.target                                                      enabled  
remote-fs.target                 

systemctl get-default:

multi-user.target

systemctl list-dependencies --reverse lightdm.service:

lightdm.service

loqs

Member

Registered: 2014-03-06

Posts: 17,321

Re: [SOLVED] Lightdm won't start on boot

systemctl get-default:

multi-user.target

systemctl list-dependencies --reverse lightdm.service:

lightdm.service

This would explain what is happening.

$ systemctl list-dependencies graphical.target

graphical.target is never reached as the default target is set to multi-user.target
Which also explains the output of "systemctl list-dependencies --reverse lightdm.service" being empty and with nothing depending on lightdm.service systemd will not attempt to start it.
Change_default_target_to_boot_into back to the default of graphical.target should resolve the issue.

k4li

Member

From: Ljubljana

Registered: 2016-04-16

Posts: 25

Re: [SOLVED] Lightdm won't start on boot

Thanx, that solved my problem.