3

I just do apt update and apt upgrade and now I can't enter GUI mode after booting (Yes, I can enter tty1-6 via Ctrl+Alt+F2). The last uprade is about the kernel, I think. Note that this error may differ from:

Why do I think this problem differs from the previous ones?

  • I tried to uninstall snap, disable nvidia persistent and change kernel, but the problem still appears.
  • I can boot into GUI if I choose recovery model (even with the same kernel)

I also already tried the solutions offered there and nothing works. I am still on this error on boot.


[  ok  ]  finished wait until snapd is fully seeded

Any offer?

sugab
  • 4,367
  • 2
    "nothing works" doesn't mean that it's a different question. Your question should clearly explain how the question is different. The single sentence of your description does not give us enough information to understand what your different problem might be. – user535733 Jan 19 '22 at 00:46
  • Thanks! I added more info. Also, I can confirm now I can enter GUI if I choose recovery mode from grub. – sugab Jan 19 '22 at 02:48
  • 2
    Im having a similar issue. I've seen this before on older lts versions and adding the nomodeset option has worked in the past. But now that isn't working. Space isn't an issue for my system. So that didn't solve the problem. For now what im doing is just booting into the old kernel. I will probably remove the old. Anyone else able to solve it? Other than remove the hot mess that is snap? – pdxmusl Sep 15 '22 at 19:19

2 Answers2

2

This happened to me when I ran out of disk space.

Solution:

  1. Boot into recovery mode
  2. Use root shell
  3. Delete files
Jakobovski
  • 131
  • 1
    The cause seems many. In my case, the (nvidia) is the culprit. Adding nomodeset option in /etc/default/grub solves my problem above. – sugab Feb 09 '22 at 07:30
  • 2
    Also, nouveau.modeset=0 on the grub setting above works fine and maybe better than nomodeset only (proper resolution) – sugab Feb 17 '22 at 06:29
0

I've encountered exact same problem when I was using Normal Installation and check in Third party software when installing Ubuntu 20.04.

The issue got resolved after I reinstalled Ubuntu 20.04 with Minimal Installation without check in Third party software

I'm not sure where exactly the problem was lying, but hope this helps!

njima1572
  • 21