Hi
After recent update system hangs (will post picture below).
I can access TTY thus the terminal under my user.
I never experienced this before.
I spend limited time using the laptop where it happened so some guidance on how to fix it quickly is appreciated.
Thanks
Please define “Manjaro DE”. Notice I’ve removed it from your topic title. We already know you’re using Manjaro, however we don’t know what DE you’re currently using.
Note that I’ve also removed your useless photo you took in portrait mode from your phone. It does not help us help you and only makes the forum storage and backups larger.
If you can access the terminal, then you probably booted fine. There’s a decent chance your desktop manager failed to launch your compositor and desktop environment, whether it’s X11/Wayland/DE-specific configuration, GPU module related, libinput, or whatever.
The errors you probably want to see are in your journalctl logs. e.g.: journalctl -b -p3 for all the errors system wide, since your last boot.
To get more specific, the output of @cscs’s inxi command provides everyone helpful info to help troubleshoot.
He mentioned that way since you are stuck in TTY mode (with no copy/paste). If you don’t want to use that pastebin type service, you can always just: inxi -Farz > inxi.out
Then copy that inxi.out file off to somewhere where you can copy/paste.
This stands out as odd.
We dont use bootsplash anywhere do we?
Did you add this yourself?
If you dont use bootsplash then I would probably suggest to remove that option.
I honestly dont know whether the path is reasonable or not even if you do use bootsplash.
I dont know for sure, but if all of your options are in the same original place that would mean editing /etc/default/grub. ex:
sudo micro /etc/default/grub
Whether after that change or not I would suggest rebuilding your initramfs and grub.
sudo mkinitcpio -P && sudo update-grub
I am also interested in a few other possibilities.
This laptop dual boots Manjaro with Zorin Lite. Zorin works fine.
I use Manjaro GRUB.
I’m sorry but I have to take picture of those commands to type them in the laptop and come back to this laptop to show the output.
Ă— lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Sat 2024-10-12 01:05:44 WEST; 36min ago
Duration: 108ms
Invocation: 770d82bca4fb4c8dadd2c1c2bbeb4a31
Docs: man:lightdm(1)
Process: 926 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
Main PID: 926 (code=exited, status=1/FAILURE)
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Start request repeated too quickly.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:44 T2310 systemd[1]: Failed to start Light Display Manager.
out 12 01:05:41 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:41 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:41 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:41 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:41 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
out 12 01:05:41 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:42 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
out 12 01:05:42 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:42 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
out 12 01:05:43 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:43 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
out 12 01:05:43 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:43 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Start request repeated too quickly.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:44 T2310 systemd[1]: Failed to start Light Display Manager.
That is an error of the script.
You can remove that lib32 package before re-entering the command.
You can then optionally re-add lib32 packages associated with mesa.
Pretty much vesa is a very generic driver. It could be seen as a sort of fall-back at one time … though in many cases today it simply breaks gfx. And thats what happened in your case - vesa was added and then graphics failed to work properly.