Kernel version didn't update when upgrading from saucy to trusty

[Shoham Peller]

After upgrading from saucy (13.10) to trusty (14.04), I've found that the kernel did not update:

$ uname -r
3.11.0-12-generic
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty

I had to manually upgrade my kernel version. See:
http://askubuntu.com/questions/451655/upgrading-to-14-04-didnt-update-my-kernel

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: vtsspp sep3_10 pax apwr3_1 nvidia
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Mon Apr 21 02:09:20 2014
InstallationDate: Installed on 2013-10-17 (184 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to trusty on 2014-04-18 (2 days ago)
VarLogDistupgradeTermlog:

[Brian Murray (brian-murray)]

There seems to be a discrepancy in versions of linux-image and linux-headers installed on the pre-upgrade system I wonder if that has something to do with it.

linux-headers-3.11.0-19 3.11.0-19.33 0
linux-headers-3.11.0-19-generic 3.11.0-19.33 0
linux-headers-generic 3.11.0.19.20 0
linux-image-3.11.0-12-generic 3.11.0-12.19 0
linux-image-extra-3.11.0-12-generic 3.11.0-12.19 0

[Shoham Peller (shoham-peller)]

Anything new regarding the issue?

[Chris Guiver (guiverc)]

Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.