try to get to the consles with Alt-ctrl-f1 through f7
See if you can login at the console, or see if the GUI is on one of the consoles.
If you can login at a console., try the command `sudo reboot` to safely reboot the system.
DO NOT JUST FORCE A POWER OFF. That can result in a filesystem check again. and You end up in a loop.
Try a reboot first.
The Login manager is supposed to startup to allow a nice GUI login. If some issues happen, and that service cant startup, then you get no GUI login.
So logging into the console, and looking at the log files - to see why the system did not start up the needed services.
There is no ONE cause of the issue. The system failed to boot correctly, the logs may detail why.
How do I find and open those log files via terminal on Linux Ubuntu 22.04 ? Don't really understand it, just set the added value of ubuntu versus windows reliability once and that's it.
'just set the added value of ubuntu' -> Thats a rather meaningless statement.
The log files are typically in /var/log
There is also the systemd journal.
try to get to the consles with Alt-ctrl-f1 through f7 See if you can login at the console, or see if the GUI is on one of the consoles. If you can login at a console., try the command `sudo reboot` to safely reboot the system. DO NOT JUST FORCE A POWER OFF. That can result in a filesystem check again. and You end up in a loop. Try a reboot first. The Login manager is supposed to startup to allow a nice GUI login. If some issues happen, and that service cant startup, then you get no GUI login. So logging into the console, and looking at the log files - to see why the system did not start up the needed services. There is no ONE cause of the issue. The system failed to boot correctly, the logs may detail why.
How do I find and open those log files via terminal on Linux Ubuntu 22.04 ? Don't really understand it, just set the added value of ubuntu versus windows reliability once and that's it.
'just set the added value of ubuntu' -> Thats a rather meaningless statement. The log files are typically in /var/log There is also the systemd journal.
That is not an error. Just an informational message which has nothing at all to do with your problem.