Baron composed on 2018-03-16 17:26 (UTC):
Felix Miata wrote:
Instead of startx, try
journalctl | grep failed
and see if it reports what failed.
If I run this now, will I get anything useful ?
If you're in a normal boot, try:
journalctl -b -1 | grep failed
instead. s/-1/-2/ if you want to look at the 2nd previous boot. Either presume Q4OS has persistent journaling enabled. Otherwise you'll get nothing useful.
If Q4OS is a Plymouth user, you might try disabling it by adding to cmdline
plymouth.enable=0
I did see something about "plymouth" when the pages of lines were flashing by.
Plymouth for most users is nothing but bling, Windows emulation, covering up boot messages with a GUI screen. Plymouth is actually useful or even required for some configurations. I don't have it installed anywhere that allows it to be removed.