Arch fails on lightdm start with DRDY ERR (blicking restart)

ev8848 · 2017-11-09 13:50:42

HI,

I just updated Arch linux and now it can't start, failing on stage where LightDm starts,
The main concern is that I can't get any logs or info at all - system blicks, no way to open any `tty`.
If I get lucky to open tty - it get interrupted with `failed command: READ FPDMA QUEUED` message

I have Arch + Ubuntu through GRUB.
In Ubuntu I can mount Arch partition and get access to files - all works fine.

I know that description look weird and too `noobish` but I can't extract any additional info)

loqs · 2017-11-09 14:10:15

Welcome to the arch linux forums ev8848.
If you change Systemd#Change_default_target_to_boot_into to multi-user.target can you access a command prompt?

ev8848 · 2017-11-09 14:46:26

I get to the prompt (while getting interrupted by printed errors) and switched off lightdm.service
Currently default target set to graphical.target
Xorg.log has one error: "failed to load `evdev`driver (module does not exist)"

It is hard to reply through mobile phone)

Last edited by ev8848 (2017-11-09 14:47:01)

seth · 2017-11-09 15:06:40

Please paste the entire Xorg log, see https://wiki.archlinux.org/index.php/Li … in_clients

ev8848 · 2017-11-09 15:09:53

here it is,
https://ptpb.pw/c5gY

seth · 2017-11-09 15:12:21

[   224.528] (II) Server terminated successfully (0). Closing log file.

X11 is fine, lightdm crashes - check the journal and its error logs.
Do you use autologin?

ev8848 · 2017-11-09 15:33:40

no, no `autologin`
/var/log/lightdm -for logs?

ev8848 · 2017-11-09 15:33:40

no, no `autologin`
/var/log/lightdm -for logs?

seth · 2017-11-09 15:43:58

Might as well be in the journal, but usually yes.
Did you configure some custom greeter (instead of the gtk one)?

ev8848 · 2017-11-09 15:50:03

here is lightdm.log : https://ptpb.pw/QFL4

it saying that it can't launch plymouth
And I haven't any other greeters

Last edited by ev8848 (2017-11-09 15:52:25)

seth · 2017-11-09 16:15:29

Is this file recent? I'm not very keen in the faulures of lightdm, but this seems to be SIGTERM'd by the init process...

ev8848 · 2017-11-09 16:46:40

Yeap,
maybe just delete lightdm and try some other display manager?

Last edited by ev8848 (2017-11-09 16:47:11)

seth · 2017-11-09 18:57:57

https://wiki.archlinux.org/index.php/Xinit

bunda · 2017-11-10 05:44:43

I was able to delete lightdm and start X + AwesomeWM manualy,
Now I have strange mouse jumping on external monitor (I am using laptop), but this can wait
So, I tried to reinstall lightdm and to launch it in test-mode, here is output :

[+0.00s] DEBUG: Logging to /home/k2/.cache/lightdm/log/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.24.0, UID=1000 PID=4197
[+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: Running in user mode
[+0.00s] DEBUG: Using Xephyr for X servers
[+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.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: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory)
[+0.02s] DEBUG: Seat seat0: Starting local X display
[+0.02s] DEBUG: XServer 1: Logging to /home/k2/.cache/lightdm/log/x-1.log
[+0.02s] WARNING: XServer 1: Failed to make authority directory /run/lightdm/root: Permission denied
[+0.02s] DEBUG: XServer 1: Writing X server authority to /run/lightdm/root/:1
[+0.02s] WARNING: XServer 1: Failed to write authority: Failed to open X authority /run/lightdm/root/:1: No such file or directory
[+0.02s] DEBUG: XServer 1: Launching X Server
[+0.02s] DEBUG: Launching process 4202: /usr/bin/Xephyr :1 -seat seat0 -auth /run/lightdm/root/:1 -nolisten tcp
[+0.02s] DEBUG: XServer 1: Waiting for ready signal from X server :1
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.02s] WARNING: Could not enumerate user data directory /var/lib/lightdm-data: Error opening directory '/var/lib/lightdm-data': Permission denied
[+0.43s] DEBUG: Process 4202 terminated with signal 11
[+0.44s] DEBUG: XServer 1: X server stopped
[+0.44s] DEBUG: XServer 1: Removing X server authority /run/lightdm/root/:1
[+0.44s] DEBUG: Seat seat0: Display server stopped
[+0.44s] DEBUG: Seat seat0: Stopping session
[+0.44s] DEBUG: Seat seat0: Session stopped
[+0.44s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.44s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+0.44s] DEBUG: Seat seat0: Stopping
[+0.44s] DEBUG: Seat seat0: Stopped
[+0.44s] DEBUG: Required seat has stopped
[+0.44s] DEBUG: Stopping display manager
[+0.44s] DEBUG: Display manager stopped
[+0.44s] DEBUG: Stopping daemon
[+0.44s] DEBUG: Exiting with return value 1

Same as it was during crashes

Last edited by bunda (2017-11-10 05:45:42)

bunda · 2017-11-10 05:56:59

So I finally get lightdm alive.
The solution was to:
uninstall lightdm, lightdm-gtk-greeter
delete /var/lib/lightdm, /var/cache/lightdm and /run/lightdm
install lightdm & greeter again

But problem with mouse pointer still occurs

seth · 2017-11-10 08:12:27

Seems to have been some corrupt cache, please remember to mark this thread as solved and open a new one for the mouse issue (where you should elaborate on "jumping", the usual fix for a jumping mouse is https://istart.com.au/wp-content/upload … trends.jpg ;-)

Arch Linux

#1 2017-11-09 13:50:42

Arch fails on lightdm start with DRDY ERR (blicking restart)

#2 2017-11-09 14:10:15

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#3 2017-11-09 14:46:26

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#4 2017-11-09 15:06:40

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#5 2017-11-09 15:09:53

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#6 2017-11-09 15:12:21

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#7 2017-11-09 15:33:40

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#8 2017-11-09 15:33:40

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#9 2017-11-09 15:43:58

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#10 2017-11-09 15:50:03

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#11 2017-11-09 16:15:29

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#12 2017-11-09 16:46:40

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#13 2017-11-09 18:57:57

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#14 2017-11-10 05:44:43

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#15 2017-11-10 05:56:59

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

#16 2017-11-10 08:12:27

Re: Arch fails on lightdm start with DRDY ERR (blicking restart)

Board footer