Comment 39 for bug 1548587

Revision history for this message
Joe Krause (d-joe-a) wrote : Re: Ubuntu 15.10 VMWare guest won't show UI after upgrading to 4.2.0-30

I hope this helps. I was trying to figure out why the resolution hiccups when I install linux-image-4.2.0-30-generic_4.2.0-30.35+lp1548587~kamal2_amd64.deb but what I think I have demonstrated is that the original bug (GUI not displaying) is due to the package: linux-image-extra-4.2.0-30-generic

Step #1
When I confirmed Kamal's kernel image, I had installed it into VMs where I had previously upgraded to 4.2.0-30 but subsequently uninstalled both linux-image-4.2.0-30 and linux-image-extra-4.2.0-30-generic like so:
sudo apt-get --purge removelinux-image-4.2.0-30 linux-image-extra-4.2.0-30-generic

I was running linux-image-4.2.0-30-generic_4.2.0-30.35+lp1548587~kamal2 along side linux-image-extra-4.2.0-27-generic and that fixed the original bug with the GUI not displaying, but caused an incidental bug where the VMWare window was resized to 8000x3200.

Step #2
I only installed half of Kamal's fix, so this time I installed a new VM with 15.10, upgraded it to 4.2.0-30, verified GUI not displaying, and then installed both the linux-image and linux-image-extra from Kamal's fix. Sure enough, the GUI displaying bug was fixed and the resolution did not tweak out like when there was a version mismatch.

Step #3
This time I installed a new VM with 15.10, upgraded to 4.20-30, verified the bug, and then only installed Kamal's image fix (not the extras package). That means I was running: linux-image-4.2.0-30-generic_4.2.0-30.35+lp1548587~kamal2 with linux-image-extra-4.2.0-30-generic. This time I still had the GUI not displaying issue - but with Kamal's new kernel image. Now I am starting to think the issue is with the linux-image-extra-4.2.0-30-generic . I advanced it to Kamal's version (linux-image-extra-4.2.0-30-generic_4.2.0-30.35+lp1548587~kamal2) and it worked! I rolled it all the way back to linux-image-extra-4.2.0-16-generic and it worked! Its only when the package is linux-image-extra-4.2.0-30-generic that it doesn't work. Again, I noticed that the resolution issue only happens when the linux-image and linux-image-extra versions are mismatched.

Step #4
To be as anal as possible, I setup a new VM and decided to try linux-image-4.2.0-30-generic with a rolled back linux-image-extra. Viola, it worked! However, due to version mismatch, the resolution issue appeared.

TL;DR (Conclusions)
linux-image-4.2.0-30-generic works with linux-image-extra-4.2.0-27-generic and linux-image-extra-4.2.0-16-generic but not with
linux-image-extra-4.2.0-30-generic

The resolution issue is really a non issue because it only happens when I use packages from different versions.

Kamal, maybe you don't want to undo the changes made in the linux-image package between 4.2.0-27 and 4.2.0-30 if the bug can be completely localized to linux-image-extra.