Comment 3 for bug 1996053

Revision history for this message
Heinrich Bjerregaard (hebj) wrote : Re: [Bug 1996053] No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works)

Unfortunately I did a lot of trial and error attempts to get my GUI back.
I installed linux-image-unsigned-5.19.0-21-generic, however, with same bad result.
During the fight I lost the image 5.15.0.
Another thing I did was upgrading TrueNas from 12.1 to 13.0-U3.1.
This process clears all the ZFS caches. Whether this has any impact upon a VM, I don't know.

So I did end up with the images 5.19.0-21 and 5.19.0.23 and they both boot ok.

Since I have been confused and inconsequent in my testing, I think you should mark the bug as an user error.

I am sorry for making this noise.

> On 28 Nov 2022, at 10.59, Daniel van Vugt <email address hidden> wrote:
>
> Also while using kernel 5.15 please run:
>
> journalctl -b0 > oldkernel.txt
> lspci -kv > lspci.txt
>
> and attach the resulting text files here.
>
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1996053
>
> Title:
> No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works)
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> I am running Ubuntu 22.04.1 on a VM under TrueNas.
> After upgrade to 22.10 I just ends up with a black screen, however, everything else like mail, dns, dhcp and apache2 works well.
>
> I am using x11vnc and in the 'journalctl -b' it seems that a display
> cannot be achieved.
>
> In the boot menu I have
> *Ubuntu, with Linux version 5.19.0-23-generic
> Ubuntu, with Linux version 5.15.0-52-generic
>
> However, if I am booting 5.15.0-52 everything is OK.
> -----
> lsb_release -rd
> Description: Ubuntu 22.10
> Release: 22.10
> -----
> cat /proc/version_signature
> Ubuntu 5.19.0-23.24-generic 5.19.7
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996053/+subscriptions
>