wily kernel version removed after upgrade to wily

[Erick Brunzell]

Looking at /var/log/dist-upgrade/apt-term.log it actually appears that the Wily kernel was purged because I was using a proprietary graphics driver:

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.2.0-16-generic
Found initrd image: /boot/initrd.img-4.2.0-16-generic
Found linux image: /boot/vmlinuz-3.19.0-30-generic
Found initrd image: /boot/initrd.img-3.19.0-30-generic
Found linux image: /boot/vmlinuz-3.19.0-14-generic
Found initrd image: /boot/initrd.img-3.19.0-14-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu 14.04.3 LTS (14.04) on /dev/sda1
Found Ubuntu Wily Werewolf (development branch) (15.10) on /dev/sda7
Found Ubuntu 15.10 (15.10) on /dev/sda8
Found Debian GNU/Linux (8.2) on /dev/sdb1
Found Ubuntu Wily Werewolf (development branch) (15.10) on /dev/sdc1
done
Removing linux-image-4.2.0-16-generic (4.2.0-16.19) ...
Examining /etc/kernel/prerm.d.
run-parts: executing /etc/kernel/prerm.d/dkms 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic
dkms: removing: nvidia-304 304.128 (4.2.0-16-generic) (x86_64)

-------- Uninstall Beginning --------
Module: nvidia-304
Version: 304.128
Kernel: 4.2.0-16-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

nvidia_304.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.2.0-16-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod....

DKMS: uninstall completed.
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic
update-initramfs: Deleting /boot/initrd.img-4.2.0-16-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.19.0-30-generic
Found initrd image: /boot/initrd.img-3.19.0-30-generic
Found linux image: /boot/vmlinuz-3.19.0-14-generic
Found initrd image: /boot/initrd.img-3.19.0-14-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu 14.04.3 LTS (14.04) on /dev/sda1
Found Ubuntu Wily Werewolf (development branch) (15.10) on /dev/sda7
Found Ubuntu 15.10 (15.10) on /dev/sda8
Found Debian GNU/Linux (8.2) on /dev/sdb1
Found Ubuntu Wily Werewolf (development branch) (15.10) on /dev/sdc1
done
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
 you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
 you may need to re-run your boot loader[grub]
Removing qtdeclarative5-ubuntu-web-plugin-assets (0.23+15.04.20150416-0ubuntu1) ...
Removing thermald (1.4.3-5) ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
[....] Stopping thermald (via systemctl): thermald.service[?25l7[ ok 8[?12l[?25h.
Removing xul-ext-webaccounts (0.5-0ubuntu4.15.04.1) ...
Removing webaccounts-extension-common (0.5-0ubuntu4.15.04.1) ...
Removing xfonts-mathml (6ubuntu1) ...
Removing libedataserver-1.2-18 (3.12.11-0ubuntu1.15.04.1) ...
Removing libcamel-1.2-49 (3.12.11-0ubuntu1.15.04.1) ...
Removing libicu52:amd64 (52.1-8ubuntu0.2) ...
Processing triggers for libc-bin (2.21-0ubuntu4) ...
Processing triggers for man-db (2.7.4-1) ...
Processing triggers for dbus (1.10.0-1ubuntu1) ...
dbus-daemon has been upgraded from a version with incompatible configuration.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubuntu-release-upgrader-core 1:15.10.10
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Tue Oct 20 13:19:17 2015
InstallationDate: Installed on 2015-04-18 (184 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150417.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago)
VarLogDistupgradeTermlog:

[Erick Brunzell (lbsolost)]

In retrospect I probably should have selected that this posed a potential security risk because the Vivid kernel may fail to upgrade properly, and even if it does Vivid will go EOL in about 3 months, so this probably should be flagged for security. Sadly I'm not sure how to do that, sorry.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1508157

[Brian Murray (brian-murray)]

From VarLogDistUpgradeMain.log we can see the following decisions being made:

2015-10-20 12:03:36,420 DEBUG Foreign:
2015-10-20 12:03:36,420 DEBUG identifyObsoleteKernels()
2015-10-20 12:03:44,628 DEBUG identifyObsoleteKernels found 'set()'
2015-10-20 12:03:44,628 DEBUG forced_obsoletes: ['desktop-effects', 'gnome-app-install', 'policykit-gnome', 'gnome-mount']
2015-10-20 12:03:45,909 DEBUG Unused dependencies: linux-image-generic libavutil54 libavcodec56 libx264-142 linux-headers-4.2.0-16 libilmbase6 linux-headers-generic libswscale3 libavformat56 libavresample2 libdirac-encoder0 libopenexr6 linux-image-4.2.0-16-generic linux-headers-4.2.0-16-generic linux-image-extra-4.2.0-16-generic thermald
2015-10-20 12:03:45,909 DEBUG remove_candidates: '{'libapt-pkg4.12', 'policykit-gnome', 'libedata-book-1.2-20', 'libswscale3', 'libufe-xidgetter0', 'libgdata19', 'libecal-1.2-16', 'xfonts-mathml', 'linux-image-extra-4.2.0-16-generic', 'thermald', 'libgnome-bluetooth11', 'libboost-iostreams1.55.0', 'libplist2', 'libavutil54', 'linux-headers-3.19.0-30', 'libavcodec56', 'libpoppler49', 'libwps-0.3-3', 'linux-headers-3.19.0-30-generic', 'qtdeclarative5-ubuntu-web-plugin-assets', 'linux-headers-generic', 'gnome-app-install', 'libboost-system1.55.0', 'libxp6', 'linux-headers-4.2.0-16-generic', 'libmircommon3', 'linux-image-3.19.0-30-generic', 'libebook-1.2-14', 'libapt-inst1.5', 'libvpx1', 'linux-headers-4.2.0-16', 'libnettle4', 'libcamel-1.2-49', 'gnome-mount', 'libboost-filesystem1.55.0', 'libopenexr6', 'libinput7', 'libgnome-control-center1', 'libebook-contacts-1.2-0', 'librhythmbox-core8', 'libvncclient0', 'libexiv2-13', 'libicu52', 'libhogweed2', 'webaccounts-extension-common', 'libx264-142', 'xul-ext-webaccounts', 'libmediaart-1.0-0', 'linux-image-generic', 'libedata-cal-1.2-23', 'libilmbase6', 'libavformat56', 'libavresample2', 'libdirac-encoder0', 'libgphoto2-port10', 'desktop-effects', 'linux-image-4.2.0-16-generic', 'libedataserver-1.2-18', 'libebackend-1.2-7', 'linux-image-extra-3.19.0-30-generic', 'libxcb-util0'}'
2015-10-20 12:03:45,910 DEBUG Start checking for obsolete pkgs
2015-10-20 12:03:52,626 DEBUG skipping running kernel pkg 'linux-headers-3.19.0-30-generic'
2015-10-20 12:03:52,626 DEBUG 'linux-headers-3.19.0-30-generic' scheduled for remove but not safe to remove, skipping
2015-10-20 12:03:54,526 DEBUG skipping running kernel pkg 'linux-image-3.19.0-30-generic'
2015-10-20 12:03:54,526 DEBUG 'linux-image-3.19.0-30-generic' scheduled for remove but not safe to remove, skipping
2015-10-20 12:04:03,470 DEBUG skipping running kernel pkg 'linux-image-extra-3.19.0-30-generic'
2015-10-20 12:04:03,470 DEBUG 'linux-image-extra-3.19.0-30-generic' scheduled for remove but not safe to remove, skipping
2015-10-20 12:04:03,745 DEBUG Finish checking for obsolete pkgs
2015-10-20 12:04:03,821 DEBUG The following packages are marked for removal: xfonts-mathml libboost-system1.55.0 libebook-contacts-1.2-0 libavformat56 libavresample2 libplist2 linux-headers-generic libmediaart-1.0-0 libgdata19 xul-ext-webaccounts libexiv2-13 libebackend-1.2-7 libicu52 linux-headers-4.2.0-16-generic libilmbase6 libboost-filesystem1.55.0 libxp6 libufe-xidgetter0 libwps-0.3-...

[Brian Murray (brian-murray)]

We can also see that the 4.2 kernel is actually installed during the upgrade:

4612 Setting up linux-image-4.2.0-16-generic (4.2.0-16.19) ...^M
4613 Running depmod.^M
4614 update-initramfs: deferring update (hook will be called later)^M
4615 Examining /etc/kernel/postinst.d.^M
4616 run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic^M
4617 run-parts: executing /etc/kernel/postinst.d/dkms 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic^M
4618 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic^M
4619 update-initramfs: Generating /boot/initrd.img-4.2.0-16-generic^M
4620 run-parts: executing /etc/kernel/postinst.d/pm-utils 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic^M
4621 run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic^M
4622 run-parts: executing /etc/kernel/postinst.d/update-notifier 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic^M
4623 run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic^M
4624 Generating grub configuration file ...^M
4625 Found linux image: /boot/vmlinuz-4.2.0-16-generic^M
4626 Found initrd image: /boot/initrd.img-4.2.0-16-generic^M
4627 Found linux image: /boot/vmlinuz-3.19.0-30-generic^M
4628 Found initrd image: /boot/initrd.img-3.19.0-30-generic^M
4629 Found linux image: /boot/vmlinuz-3.19.0-14-generic^M
4630 Found initrd image: /boot/initrd.img-3.19.0-14-generic^M
4631 Found memtest86+ image: /boot/memtest86+.elf^M
4632 Found memtest86+ image: /boot/memtest86+.bin^M

I've been unable to recreate the removal of the kernel on a virtual machine with only 1 operating system with or without the nvidia-304 package installed.

[Brian Murray (brian-murray)]

Bug 1470577 is another case of the upgraded kernel being considered an "Unused dependency", however in that upgrade there were a plethora of issues contacting the mirror. This is something we don't see in this bug.

Bug 1315978 is another case of the upgraded kernel being considered an "Unused dependency", but there is nothing to indicate why in the log files.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[zob (zob)]

Happened to me too after final release. I too have propietary nvidia drivers on the machine in question. I added my logs with ubuntu-bug (I think).

[Brian Murray (brian-murray)]

@zob your logs were not added, could you please open a new bug report (using ubuntu-bug ubuntu-release-upgrader-core) and I'll mark it as a duplicate if it is one. Thanks!

[Bryan Quigley (bryanquigley)]

If you're installing a proprietary driver using the GUI it might be this bug instead - Bug 1506169 instead

[Erick Brunzell (lbsolost)]

That other bug that Bryan posted about made me do some digging in an install that had been affected by unrelated bug #1489147.

I was using the same hardware as in this bug and had to use the boot parameter nomodeset to even get casper/ubiquity to run w/o a black screen - this resulted in a completed install that only offered 1024X768 rather than the preferred 1366X768 resolution so I tried to install the proprietary driver using the UI which seemed to work but now the system is borked.

From a lateral install I just looked at the apt/history.log:

Start-Date: 2015-10-21 18:20:36
Commandline: aptdaemon role='role-commit-packages' sender=':1.54'
Install: fakeroot:amd64 (1.20.2-1ubuntu1, automatic), screen-resolution-extra:amd64 (0.17.1, automatic), libstdc++-5-dev:amd64 (5.2.1-22ubuntu2, automatic), lib32gcc1:amd64 (5.2.1-22ubuntu2, automatic), libjansson4:amd64 (2.7-1ubuntu1, automatic), libcuda1-304:amd64 (304.128-0ubuntu1, automatic), dkms:amd64 (2.2.0.3-2ubuntu6, automatic), nvidia-settings:amd64 (352.21-0ubuntu1, automatic), libalgorithm-diff-xs-perl:amd64 (0.04-3build1, automatic), dpkg-dev:amd64 (1.18.2ubuntu5, automatic), libalgorithm-merge-perl:amd64 (0.08-2, automatic), nvidia-304:amd64 (304.128-0ubuntu1), amd64-microcode:amd64 (2.20141028.1), ocl-icd-libopencl1:amd64 (2.2.7-2, automatic), g++:amd64 (5.2.1-3ubuntu1, automatic), libalgorithm-diff-perl:amd64 (1.19.03-1, automatic), nvidia-opencl-icd-304:amd64 (304.128-0ubuntu1, automatic), libfakeroot:amd64 (1.20.2-1ubuntu1, automatic), g++-5:amd64 (5.2.1-22ubuntu2, automatic), build-essential:amd64 (12.1ubuntu2, automatic), libc6-i386:amd64 (2.21-0ubuntu4, automatic), libxnvctrl0:amd64 (352.21-0ubuntu1, automatic), pkg-config:amd64 (0.28-1ubuntu1, automatic)
Remove: linux-generic:amd64 (4.2.0.16.18)
End-Date: 2015-10-21 18:22:55

So, why would installing the tested nvidia driver remove linux-generic? Maybe this snippet from the term.loog would be helpful:

Log started: 2015-10-21 18:20:36
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 154143 files and directories currently installed.)
Removing linux-generic (4.2.0.16.18) ...
Selecting previously unselected package libjansson4:amd64.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading ...

[zob (zob)]

@brian-murray

Done. New possibly duplicate report is here: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1509305

[Erick Brunzell (lbsolost)]

Just checked the forums this AM and four other people report the same issue:

http://ubuntuforums.org/showthread.php?t=2299964

And more Wily kernel + nVidia woes:

http://ubuntuforums.org/showthread.php?t=2300068&p=13377864&posted=1#post13377864

[Brian Murray (brian-murray)]

Comment #11 is addressed in bug 1506169 for which I've created a fix.

[Brian Murray (brian-murray)]

I've recreated this by removing linux-generic and not running sudo apt-get remove, so the root cause is the same as bug 1509305. Given that bug 1509305 is more succinct, I'm going to mark this as a duplicate of that.