Skip to main content ↑ ↓
Topic: [BUG-REPORT] LightDM will not start on system boot. (Read 758 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

[BUG-REPORT] LightDM will not start on system boot.

Hello, I recently moved from SDDM to LightDM. SDDM was working fine.

I installed lightdm-runit (since I use runit) and a lightdm greeter, Then I ran "ln -s /etc/runit/sv/lightdm /run/runit/service" to enable the service and then rebooted. Once my system starts it drops me into a TTY without dropping me into lightdm. If I run "sudo lightdm" it drops me into lightDM and everything works as intended. I would also like to note that I must use sudo and I cant run lightdm by itself. I am not sure if this is normal or not.

I am using x11 and artix runit

Output of sudo sv status lightdm: run: lightdm: (pid 9661) 2s; run: log: (pid 1534) 4892s
It also shows up on ps aux on boot.

I would also like to mention that it appears that pulse audio is broken since I moved from SDDM to LightDM, I cannot hear sound from a browsers anymore and bubblewrap gives me this error "bwrap: Can't find source path /run/user/1000/pulse: No such file or directory". Don't know why SDDM/LightDM would affect this.

Loginctl logout also seems to have broke.

No clue what the issue is, any help is highly appreciated.

Edit: I would like to also add loginctl shutdown/restart appears to be broken too, the system hangs for 5-10 seconds before shutting down unlike before with sddm.

Edit 2: I noticed that after a reboot and after clearing the logs in /var/log/lightdm/. No logs are generated until I manually run sudo lightdm in the tty. I suspect this may be something up with runit or lightdm-runit. It seems like lightdm isn't even being executed even though sv is showing the script as running.

Output of ps aux | grep 'lightdm'
Code: [Select]
root      1493  0.0  0.0   2368  1364 ?        Ss   21:04   0:00 runsv lightdm
root      1518  0.0  0.0   2520   812 ?        S    21:04   0:00 svlogd -tt /var/log/lightdm
<REDACTED>     3839  0.0  0.0   6568  2424 tty1     S+   21:06   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox lightdm

Edit 3: I have made a very strange discovery, if I boot my system and let it sit there without touching it for 5 minutes, it just mysteriously opens lightDM by itself and everything works as intended, the audio issues from above were fixed, the loginctl issues were fixed, etc. I'm very very very confused of what this could be. Obviously this is still a major issues because I need lightdm to start up instantly, I can't wait 5 minutes for it to just sit there.

Re: LightDM will not start on system boot. [Urgent]

Reply #1 –
I have tried SDDM again just to make sure it's an issue with lightDM. I reinstalled and re-setup SDDM and it works completely fine. I suspect this is a glitch with "lightdm-runit" as other display managers are not exhibiting the same issues.
I have marked this thread as a bug report.

Re: [BUG-REPORT] LightDM will not start on system boot.

Reply #2 –
There should be logs in, I think, /var/log/lightdm. Have a look, post them. I can't remember if they are time stamped but it might shed some light?

I'm curious. Why not just use sddm if it works ? What's it missing that lightdm has ?

Re: [BUG-REPORT] LightDM will not start on system boot.

Reply #3 –
Quote from: gripped – on
There should be logs in, I think, /var/log/lightdm. Have a look, post them. I can't remember if they are time stamped but it might shed some light?

I'm curious. Why not just use sddm if it works ? What's it missing that lightdm has ?
My problem with SDDM is that the majority of themes require plasma core to be installed, and I use a window manager and not a DE.

/var/log/lightdm/lightdm.log output (I think this is when I manually ran it with sudo lightdm because no logs appear if I dont manually run it)
Code: [Select]
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=2598
[+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: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+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 has property CanMultiSession=no
[+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.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: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.01s] DEBUG: XServer 0: Launching X Server
[+0.01s] DEBUG: Launching process 2604: /usr/bin/X :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.04s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.04s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.06s] DEBUG: Seat seat0 changes active session to
[+0.86s] DEBUG: Got signal 10 from process 2604
[+0.86s] DEBUG: XServer 0: Got signal from X server :0
[+0.86s] DEBUG: XServer 0: Connecting to XServer :0
[+0.87s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.87s] DEBUG: Session pid=2639: Started with service 'lightdm-greeter', username 'lightdm'
[+0.88s] DEBUG: Session pid=2639: Authentication complete with return value 0: Success
[+0.88s] DEBUG: Seat seat0: Session authenticated, running command
[+0.88s] DEBUG: Session pid=2639: Running command /usr/bin/lightdm-webkit2-greeter
[+0.88s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.88s] DEBUG: Session pid=2639: Logging to /var/log/lightdm/seat0-greeter.log
[+0.88s] DEBUG: Activating VT 7
[+1.20s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false
[+1.52s] DEBUG: Greeter requests data directory for user redacted
[+1.52s] DEBUG: Creating shared data directory /var/lib/lightdm-data/redacted
[+3.56s] DEBUG: Greeter start authentication for redacted
[+3.56s] DEBUG: Session pid=2768: Started with service 'lightdm', username 'redacted'
[+3.57s] DEBUG: Session pid=2768: Got 1 message(s) from PAM
[+3.57s] DEBUG: Prompt greeter with 1 message(s)
[+3.59s] DEBUG: Continue authentication
[+3.63s] DEBUG: Session pid=2768: Authentication complete with return value 0: Success
[+3.63s] DEBUG: Authenticate result for user redacted: Success
[+3.63s] DEBUG: User redacted authorized
[+3.63s] DEBUG: Greeter requests session i3
[+3.63s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+3.63s] DEBUG: Session pid=2639: Sending SIGTERM
[+3.66s] DEBUG: Session pid=2639: Exited with return value 0
[+3.66s] DEBUG: Seat seat0: Session stopped
[+3.66s] DEBUG: Seat seat0: Greeter stopped, running session
[+3.66s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+3.66s] DEBUG: Session pid=2768: Running command /etc/lightdm/Xsession i3
[+3.66s] DEBUG: Creating shared data directory /var/lib/lightdm-data/redacted
[+3.66s] DEBUG: Session pid=2768: Logging to .xsession-errors
[+3.66s] DEBUG: Activating VT 7

Re: [BUG-REPORT] LightDM will not start on system boot.

Reply #4 –
From memory there's more than one log in there.
I don't see why there would be no logs when started as a service. But maybe?

You don't have to use either. I just use startx as for my use case display managers add no value.
https://wiki.archlinux.org/title/Xinit  (you'd need to start dbus, ask if you are going to go down this road)

sddm needs some qt5 stuff but I think only drags in plasma if you also install sddm-kcm, which makes sense. sddm-kcm is optional (at least I think so).

Edit: Sorry I missed the themes bit. Use one that doesn't and figure out what's wrong with lightdm at your leisure when it's not 'Urgent' as per the thread title
Edit2: Swear it said urgent before ? :)

Re: [BUG-REPORT] LightDM will not start on system boot.

Reply #5 –
Quote from: gripped – on
From memory there's more than one log in there.
I don't see why there would be no logs when started as a service. But maybe?

You don't have to use either. I just use startx as for my use case display managers add no value.
https://wiki.archlinux.org/title/Xinit  (you'd need to start dbus, ask if you are going to go down this road)

sddm needs some qt5 stuff but I think only drags in plasma if you also install sddm-kcm, which makes sense. sddm-kcm is optional (at least I think so).

Edit: Sorry I missed the themes bit. Use one that doesn't and figure out what's wrong with lightdm at your leisure when it's not 'Urgent' as per the thread title
Edit2: Swear it said urgent before ? :)
Hey, yes I changed it from Urgent to Bug-Report. Since I determined this is most likely a glitch with the package "lightdm-runit". After deleted /var/log/lightdm folder and rebooted my computer, the only files that appear are "lock" and "current" which are empty, no logs are generated until I manually run "sudo lightdm" while sv is showing everything as up (refer to the original post).
Thanks
I also would like to apologize for being impatience by putting "urgent" since I wasn't getting any replies.

I'm also thinking of trying out lemurs instead of lightdm.

Re: [BUG-REPORT] LightDM will not start on system boot.

Reply #6 –
Quote from: widen1563 – on
After deleted /var/log/lightdm folder and rebooted my computer, the only files that appear are "lock" and "current" which are empty, no logs are generated until I manually run "sudo lightdm"
Is that the case even if you wait the 5 minutes for it to start ?
 

Re: [BUG-REPORT] LightDM will not start on system boot.

Reply #8 –
There's not more I can add as I don't use runit or lightdm.

Maybe read up on how you can log the runit boot process, if indeed you can ?

Re: [BUG-REPORT] LightDM will not start on system boot.

Reply #9 –
Quote from: gripped – on
There's not more I can add as I don't use runit or lightdm.

Maybe read up on how you can log the runit boot process, if indeed you can ?

Understandable thanks anyway!
I have switched back to SDDM and I have determined the issue with lightdm is most likely a glitch with the run script.
May I ask are you aware of SDDM themes that do not require plasma core to be installed?
Is there a SDDM port that looks like this? https://github.com/NoiSek/Aether

Re: [BUG-REPORT] LightDM will not start on system boot.

Reply #10 –
Quote from: widen1563 – on
May I ask are you aware of SDDM themes that do not require plasma core to be installed?

As far as I remember you can use it without any themes.
https://aur.archlinux.org/packages/archlinux-themes-sddm only seems to depend on sddm.
Search sddm on the aur and you can look at the dependencies.

Me I'm quite happy with my autologin to a tty and then my startx alias of 'sx' to fire up plasma.  :D

Re: [BUG-REPORT] LightDM will not start on system boot.

Reply #11 –
I use the sddm-theme-artix theme without any plasma stuff installed and it works well.
My main environment is Openbox window manager started with SDDM through dinit.