Sign up ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Somehow I got a 12.04 server to stop updating the kernel. It's stuck at 3.2.0-24-generic and doesn't want to fetch any new updates. The new kernel at the moment is 3.2.0-29

apt-get clean && sudo apt-get autoremove 
apt-get -f install
apt-get update
apt-get dist-upgrade

Shows "0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded." There were no failed installs. /var/log/aptitude doesn't show any errors

My sources.list:

###### Ubuntu Main Repos
deb precise main restricted
deb-src precise main restricted

###### Ubuntu Update Repos
deb precise-security main restricted
deb precise-updates main restricted
deb-src precise-security main restricted
deb-src precise-updates main restricted

###### Ubuntu Partner Repo
deb precise partner
deb-src precise partner

Anyone know what's wrong? Thanks

share|improve this question
try sudo apt-get dist-upgrade –  atenz Aug 13 '12 at 16:07
The list of commands I posted already has apt-get dist-upgrade, and I am running all of them as root. –  Budric Aug 13 '12 at 16:12

1 Answer 1

up vote 9 down vote accepted

You have probably removed linux metapackage by accident. If so, that should be fixed by:

sudo apt-get install linux

Further explanation:

Because of technical reasons it's not wise for the kernels to be upgraded and replaced with the new one (i.e. let's say if the new one fails you may still boot into the old one).
Thus they are packaged under the names like linux-image-3.2.0-24-generic.

So, if you upgrade the system, technically there is no update to this version! Unless you install the linux metapackage which always depends on the latest kernel, meaning that whenever an update to the kernel is available, linux will change version, and it will depend on the newer kernel, and thus the new kernel will be automatically installed.

Remember that your older kernel won't be removed this way, which is a good thing. If you find anything odd you may boot into the old one (grub -> Previous versions or something like that) and remove the new kernel.

share|improve this answer
At the very least this installed the new kernel. I'll see when the next kernel comes out if dist-upgrade works, but I think you're right. Thanks. –  Budric Aug 13 '12 at 17:48
By default, the linux metapackage is actually not installed. But the linux-image-generic metapackage (or whatever other metapackage for the particular flavor of kernel the OS was installed with). In this case, linux-image-generic was probably uninstalled to produce this problem. –  Eliah Kagan Aug 13 '12 at 20:26
I have had the same issue on ubuntu 12.04.1 on a clean install which probably means linux was not packaged as part of the release to begin with. –  Azizur Oct 21 '12 at 12:12
For me it it was apt-get install linux-generic that solved this problem for me on 14.04.… –  David Oct 12 '14 at 13:33

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.