I've been running Ubuntu 20.04.3 LTS on my Lenovo Thinkpad T14 for around a year now with little to no issue. However, very recently I have been experiencing issues with ubuntu-desktop not loading on boot.
Occasionally when I boot my machine I will be met with a black screen with a cursor flashing in the top left corner (rather than booting to the log in screen). Thus far I have managed to fix this by going to tty5 or tty6, logging in and using the command apt-get install --reinstall ubuntu-desktop
. After rebooting, the system then tends to boot to the desktop as normal. I say tends as it is not always the case, e.g., today I had to reinstall ubuntu-desktop twice before it worked.
One possible cause that I can see is I have a Nvidia MX330 graphics card, which has not played so nicely with my machine in the past. For instance I previously upgraded the driver for the card and could no longer boot my machine until I rolled back the upgrade. Moreover, I recently purged all of the Nvidia packages from my machine apt-get purge nvidia*
and now my machine runs a lot smoother!
I am wondering if anyone has any ideas as to why ubuntu-desktop would be sporadically breaking or as to ways to debug this issue? I checked my update logs less /var/log/apt/history.log
and it doesn't seem to correlate with recent updates.
Update 31/08
My issue has seemingly evolved slightly. No longer to I need to reinstall ubuntu-desktop but now when I am stuck at the black screen I can simply switch to tty5 and then back to tty1 and the desktop environment will load. It is a bit strange but it works. Just to clarify I want to understand why my boot is not working properly (although the extent to which it is not working has now changed quite a bit).
I actually don't care so much about the official Nvidia drivers for the graphics card, since switching to the nouveau driver my battery life is longer, the laptop is a lot cooler and everything runs smoother.
The kernel I am currently booting is Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
. Looking at the update logs I am fairly reasonably certain that the problems did start after a kernel upgrade.