Login screen not showing till you hold any key

plymouth
update
deepin
lightdm

#1

After the latest stable update (2018-04-28) the login screen no longer shows in Manjaro Deepin.

No error messages are printed, only the usual stuff when booting up. It simply doesn’t pass the latest screen, although the computer is still responsive to the shutdown button.

Weird enough, holding any key brings up the login screen. I’m seeing if other solutions in this forum work.


[Stable Update] 2018-04-28 - Kernels, Cinnamon, Browsers, Mesa, KDE Apps, KDE Framework, Virtualbox
Bootzeit länger als normal (subjektives Gefühl?)
[SOLVED] Where can I find the iso file to download for Manjaro 17.1.6?
[Stable Update] 2018-04-28 - Kernels, Cinnamon, Browsers, Mesa, KDE Apps, KDE Framework, Virtualbox
[Stable Update] 2018-04-28 - Kernels, Cinnamon, Browsers, Mesa, KDE Apps, KDE Framework, Virtualbox
Boot stuck until key is pressed
#2

In the Terminal application, if I enter:
sudo lightdm --test-mode --debug

I get:

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=1331
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-deepin.conf
[+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 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: 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 1
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 1
[+0.01s] DEBUG: XServer 1: Logging to /var/log/lightdm/x-1.log
[+0.01s] DEBUG: XServer 1: Can't launch X server Xephyr, not found in path
[+0.01s] DEBUG: XServer 1: X server stopped
[+0.01s] DEBUG: Releasing VT 1
[+0.01s] DEBUG: Seat seat0: Display server stopped
[+0.01s] DEBUG: Seat seat0: Can't create display server for greeter
[+0.01s] DEBUG: Seat seat0: Session stopped
[+0.01s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.01s] DEBUG: Seat seat0: Stopping
[+0.01s] DEBUG: Seat seat0: Stopped
[+0.01s] DEBUG: Failed to start seat: seat0

#3

did you try to add in /etc/environment
DISPLAY=:1
or something like that ?


#4

That hasn’t worked.


#5

have you checked any .pacnew ?


#6

With root privileges, in the folder “/”, if I search for “.pacnew” or “.pacsave” I only get one result. Which is for pacman mirrors.


#7

Have same problem after this update.
Now I‘m searching for a solution.
I‘m on Manjaro I3 community edition


#8

If I enable a verbose startup, no process is shown to fail.


#9

None of the solutions in this forum seemed to work.


#10

What happens if you switch TTY then go back to the default one ?


#11

On where the login screen should be, if you press “control + alt + F12” it brings you to the terminal. Then if you press “control + alt + F1” it shows you the login screen.


#12

And after that you can enter the user and password on log in or is still failing ?


#13

Then it works.

Interestingly enough you can bring the login screen just by holding any key. So rather than LightDM not starting, it’s rather not showing till it registers some key pressing.


#14

At least is not in a zombie/death mode, but yet still find it strange is not showing up as it should …


#15

I haven’t found a solution in Google.


#16

Reported upstream.


#17

Maybe kernel problem, if you are on Haswell platform.


#18

No it’s Sandy.


#19

Reproducible using any kernel. Tested on:

  • 4.16
  • 4.14
  • 4.1

The version 3 line didn’t work.


#20

Unitl now, I haven’t found a solution, too.
I will continue watching this post and hoping someone can give us a good hint.

Btw, I assume this post is related to the same problem: