plymouth hang - login to console not possible
This document (000019595) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 15 SP1
SUSE Linux Enterprise Server SP4
Plymouth might be unable to quit and hangs.
This affects the start of systemd services that are normally started subsequent to Plymouth,
in this case here: systemd starting X Display Manager.
At the end of booting up, the display manager fails to load and console login isn't possible.
Remote login is possible so ssh can be used to login and diagnose the issue.
"zypper ps -s" shows the plymouth-start service hanging, unable to quit:
# zypper ps -s
The following running processes use deleted files:
PID | PPID | UID | User | Command | Service
351 | 1 | 0 | root | plymouthd (deleted) | plymouth-start
The command "systemctl list-jobs" shows the plymouth-quit-wait.service running:
# systemctl list-jobs
JOB UNIT TYPE STATE <job_id>plymouth-quit-wait.service
After a successful test the option can be added permanently to the grub2 bootloader (through YaST or directly to the GRUB_CMDLINE_LINUX_DEFAULT in "/etc/default/grub").
Another option is to run the command "plymouth quit" when the system is running into this state.
Also connecting the machine to a monitor might be an option for some.
Plymouth as a graphical boot system and logger isn't really needed, unless a graphical boot animation, splash screen is needed on boot up. Hence disabling the service is considered a useful workaround.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000019595
- Creation Date: 20-Mar-2020
- Modified Date:20-Mar-2020
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: email@example.com