this post was submitted on 08 Jan 2024
11 points (100.0% liked)

Linux Questions

1069 readers
4 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

Tips for giving and receiving help

Any rule violations will result in disciplinary actions

founded 1 year ago
MODERATORS
 

For reference I use MX Linux with Systemd enabled.

I'm pretty new to Linux and have been running this for around a month. Everything was perfectly fine until yesterday (7th) when, on booting, I saw a glimpse of the logon screen for a second and was then taken to a black screen with some white text that read "[7.300130]". Searching for this number doesn't bring up anything.

Eventually I found that I could get into a terminal here by pressing ALT+F1. I also found a lot of people suggesting that if you get past grub and then have a very similar problem (blank screen, flashing cursor rather than a number) then it could be graphics drivers so I uninstalled and reinstalled them to no avail.

Somewhat embarrassingly, the eventual solution was very simple. After I opened the terminal with ALT+F1 I could get back to the GUI with ALT+SHIFT+F7 and.. everything was fine.

Still though, whenever I boot now, I get a glimpse of the logon page, then the black screen with the number, and then doing the shortcuts above gets me back to the logon screen and after that everything is normal.

My first instinct is to say some update on the 6th must have caused this. I have checked /var/log/apt/history.log and I did run apt upgrade on the 6th but the only update was to mx-welcome which I don't think is relevant.

Although it's only a minor nuisance I would like to not have to do this every time I boot. Any idea what this is?

you are viewing a single comment's thread
view the rest of the comments
[–] honeyontoast@lemmy.world 1 points 10 months ago

Just as a little update - I'm still not sure what caused it (although it does definitely seem to be systemd being a little odd because I temporarily reverted to sysvinit and it didn't happen) but today I ran sudo apt autoremove and after restarting the problem went away. It seems something left over by an old app just.. made this happen.