Plymouth just appears to be the last thing shown here https://i.imgur.com/YRujoRR.jpg …
Its possible its failing to terminate … I’ve seen it be the cause of failed boots before.
If you dont intend on using it then consider removing the associated packages.
(and removing it from initramfs at /etc/mkinitcpio.conf if it exists - then sudo mkinitcpio -P)
I’ve noticed that your system reported a hardware error. While this should not prevent machine from booting, maybe you should check it,
You can alse check the output of system journal (type journalctl and press “end” key to see recent entries). It shows more information than dmesg. It may be that your system is booting but X.org (or wayland or display manager) fails to start.
You can switch to different TTY when you see black screen by pressing CTRL+ALT+F2, and CTRL+ALT+F7 should bring you back to GUI session. In fact you can try to start another GUI session from TTY2 this way, at least when using xorg.
I successfully disabled plymouth (by adding the commands to grub) but now the boot process is stuck at “Reached Target Graphical Interface” . The mouse appears and functions but nothing else. The attached screenshot is the last screen and nothing progresses beyond it.
can you in the stuck screen enter into tty, by pressing: ctrl+alt+f2 or f1-f6 keys, enter your username and password, and type: startx
and take a picture of it…
also post pic of: mhwd-kernel -li mhwd -l -li
if you cant, post the output of the 2 commands, not the startx one from chroot…
and what did you do prior to the stuck screen? installing/ updating/ uninstalling … etc?
When I used ‘sudo startx’ it booted into the root GUI normally however my browser refused to run, dolphin ran but did not respond properly. I did manage to uninstall a few unnecessary programs using the ‘add/remove’ button while in the root GUI. System settings are accessible in root GUI.
I don’t remember what I did before this problem started but yes, the problem had started after installing and running kernel 6.3, after which I had switched to kernel 6.2 and everything was running ok. However I had switched back to kernel 6.3 after it updated recently, and this problem re-started and did not resolve itself after that, even when I tried logging in using 6.2 or 6.1 or the fallback initrams of 6.3, 6.2, 6.1.
Thanks. Yes, the hardware errors are not the cause.
StartX works but only when I execute ‘sudo startx’ at tty1 or tty2. If I execute just ‘startx’ at tty1 or tty2, I get a blank screen and error messages.
I posted the results of startx (without sudo) to Brahma’s message, but here it is again.
Well,did you check if you ran out of disk space? XFCE sometimes still boots, but Plasma needs more bytes to write. Another option is to check if your home directory is still owned by the user and not got some files it has no access to. ls -lashi . would give you an info of the current directory. Maybe poke around. sudo pacman -Scc wouild clean your pacman cache and create some space.