Plymouth errors, Could not start Display server on vt 1

[curato]

system gets stuck before splash screen after a clean reinstall of KDE 5.27.4, kernel 6.1.29-1

Cannot load any terminals or restart the display. ctrl+alt+delete works, what restarts the system. then loads system without any errors

May 21 19:45:53 user sddm[556]: Could not start Display server on vt 1
May 21 19:45:53 user sddm[556]: Attempt 3 starting the Display server on vt 1 failed
May 21 19:45:53 user sddm[556]: Display server stopping...
May 21 19:45:53 user sddm[556]: Failed to read display number from pipe
May 21 19:45:53 user sddm[556]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{<UUID>} -noreset -displayfd 17
May 21 19:45:53 user sddm[556]: Adding cookie to "/var/run/sddm/{<UUID>}"
May 21 19:45:53 user sddm[556]: Display server starting...
May 21 19:45:51 user sddm[556]: Attempt 2 starting the Display server on vt 1 failed
May 21 19:45:51 user sddm[556]: Display server stopping...
May 21 19:45:51 user sddm[556]: Failed to read display number from pipe
May 21 19:45:51 user sddm[556]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{<UUID>} -noreset -displayfd 17
May 21 19:45:51 user sddm[556]: Adding cookie to "/var/run/sddm/{<UUID>}"
May 21 19:45:51 user sddm[556]: Display server starting...
May 21 19:45:49 user sddm[556]: Attempt 1 starting the Display server on vt 1 failed
May 21 19:45:49 user sddm[556]: Display server stopping...
May 21 19:45:49 user sddm[556]: Failed to read display number from pipe
May 21 19:45:48 user sddm[556]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{<UUID>} -noreset -displayfd 17
May 21 19:45:48 user sddm[556]: Adding cookie to "/var/run/sddm/{<UUID>}"
May 21 19:45:48 user sddm[556]: Display server starting...
May 21 19:45:48 user sddm[556]: Loading theme configuration from ""
May 21 19:45:48 user sddm[556]: Adding new display on vt 1 ...
May 21 19:45:48 user sddm[556]: Logind interface found
May 21 19:45:48 user sddm[556]: Starting...
May 21 19:45:48 user sddm[556]: Initializing...

May 21 19:45:48 user systemd[1]: Started Simple Desktop Display Manager.

May 21 19:45:48 user systemd[1]: Failed to start Terminate Plymouth Boot Screen.
May 21 19:45:48 user systemd[1]: plymouth-quit.service: Failed with result 'timeout'.
May 21 19:45:48 user systemd[1]: plymouth-quit.service: start operation timed out. Terminating.

[cscs]

Remove plymouth then?

Well… you can test with some boot parameters:

plymouth.enable=0 disablehooks=plymouth

You can add this to options during boot from grub if you hit ‘e’ at selection.
You can also apply it persistently by editing /etc/default/grub and adding to the GRUB_CMDLINE_LINUX line. ex:

GRUB_CMDLINE_LINUX="plymouth.enable=0 disablehooks=plymouth"

Then run:

sudo update-grub

And reboot.

To remove it completely:

Uninstall:

sudo pacman -Rns plymouth plymouth-theme-manjaro

(im not sure which all packages you have - edit as necessary)

Also check if its set in mkinitcpio

grep plymouth /etc/mkinitcpio.conf

If it does conatain plymouth in the hooks or modules lines you can remove it.

If edited make sure to run:

sudo mkinitcpio -P

You can also remove those plymouth options from /etc/default/grub if you previouly used those.

And lastly run a grub update:

sudo update-grub

And reboot of course.

[curato]

ok ty. i removed it

looks fixed and i can see errors now on boot

idk y its default installed. causes nothing but issues and future issues hiding all errors from the end user

[cscs]

Slows down boot, isnt compatible with all setups … yeah I’m not a fan either.

Though I do like my silent boot. On faster systems displaying the boot text can itself be a bottleneck.
So I prefer it black unless it encounters a problem.

https://wiki.archlinux.org/title/Silent_boot