Autoremove Kernels

**v3.xx** · August 4th, 2015

Yes, /etc/apt/apt.conf.d/01autoremove-kernels is generated by /etc/kernel/postinst.d/apt-auto-removal and explains why the one kernel is showing up in autoremove. The other two (now three) and on hold in /01autoremove-kernels. And why it looked like it was working till a fourth kernel was added. /etc/kernel/postinst.d/apt-auto-removal needs to be modified, not removed.

**v3.xx** · August 4th, 2015

Going to try this for a while. Got no idea about this.
/etc/apt/apt.conf.d/01autoremove

The old

Code:

APT
{
  NeverAutoRemove
  {
    "^firmware-linux.*";
    "^linux-firmware$";
  };

  VersionedKernelPackages
  {
    # linux kernels
    "linux-image";
    "linux-headers";
    "linux-image-extra";
    "linux-signed-image";

The new

Code:

APT
{
  NeverAutoRemove
  {
    "^firmware-linux.*";
    "^linux-firmware$";
    "^linux-image";
    "^linux-headers";
    "^linux-image-extra";
    "^linux-signed-image";
  };

  VersionedKernelPackages
  {
    # linux kernels
    #"linux-image";
    #"linux-headers";
    #"linux-image-extra";
    #"linux-signed-image";

**QDR06VV9** · August 4th, 2015

Originally Posted by runrickus

If you would keep us abreast of your new method!
I could be be wrong here, but there is another text file "/etc/apt/apt.conf.d 01autoremove" and "/etc/apt/apt.conf.d autoremove-kernels"
That may or may not have future problems to the system?
So Please keep this thread updated if you would be kind enough.
Regards

Seems it did rare it's ugly head

Originally Posted by v3.xx

Going to try this for a while. Got no idea about this.
/etc/apt/apt.conf.d/01autoremove

The old

Code:

APT
{
  NeverAutoRemove
  {
    "^firmware-linux.*";
    "^linux-firmware$";
  };

  VersionedKernelPackages
  {
    # linux kernels
    "linux-image";
    "linux-headers";
    "linux-image-extra";
    "linux-signed-image";

The new

Code:

APT
{
  NeverAutoRemove
  {
    "^firmware-linux.*";
    "^linux-firmware$";
    "^linux-image";
    "^linux-headers";
    "^linux-image-extra";
    "^linux-signed-image";
  };

  VersionedKernelPackages
  {
    # linux kernels
    #"linux-image";
    #"linux-headers";
    #"linux-image-extra";
    #"linux-signed-image";

I am still hopeful for your efforts.

Not to sound negative or harsh, But I think you are going to be chasing your tail on this one(keeping kernels).
I really hope I am wrong on this.
Best Regards

**Alan F** · August 4th, 2015

On my system, Ubuntu Mate, 64 bit, 15.10 fully updated, I have always removed all 'autoremove' suggestions by Synaptic, reducing the number of kernels installed to one.

However with 4.1.0-3.3 now the current kernel, I still have 4.1.0-2.2 available in Grub and no 'autoremove' suggestion

Maybe someone has fixed this problem

**v3.xx** · August 5th, 2015

Originally Posted by Alan F

On my system, Ubuntu Mate, 64 bit, 15.10 fully updated, I have always removed all 'autoremove' suggestions by Synaptic, reducing the number of kernels installed to one.

However with 4.1.0-3.3 now the current kernel, I still have 4.1.0-2.2 available in Grub and no 'autoremove' suggestion

Maybe someone has fixed this problem

And 4.1.0-2.2 did not show up as installed in synaptic? Maybe update grub.

Code:

sudo update-grub

On a side note, I just updated 12.04 and have a kernel showing up in autoremove.

**Cavsfan** · August 6th, 2015

Originally Posted by v3.xx

And 4.1.0-2.2 did not show up as installed in synaptic? Maybe update grub.

Code:

sudo update-grub

On a side note, I just updated 12.04 and have a kernel showing up in autoremove.

Yes, it happens on all Ubuntu Versions now. I only have the 4.1.0-3-generic on both my 15.10 Mate and reg. Ubuntu 15.10.

Code:

cavsfan@cavsfan-MS-7529:~$ uname -r
4.1.0-3-generic

Alan F if you were able to retain 2 kernels, you would be the only one I know of. I was not able to even when the 4.0 kernels started being introduced.

As I previously stated when you even manually delete say the 3rd kernel that is on your system.
That still triggers /etc/kernel/postinst.d/apt-auto-removal which will then in turn jumble etc/apt/apt.conf.d/01autoremove-kernels around until you have one kernel left.
Manually deleting a kernel should definitely not trigger a reboot and /etc/kernel/postinst.d/apt-auto-removal but it does nevertheless.

**Cavsfan** · August 6th, 2015

Here is the thread I initially posted. I thought it was just Utopic but then it went to everything including Trusty.

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

Here is the bug report I filed about it: https://bugs.launchpad.net/ubuntu/+s...t/+bug/1440608

It now has I think me and 6 other people and is listed as status: confirmed, importance: high but is not assigned to anyone.

IMO the problem is that they are working with phones that cannot store more than one kernel but, that should not include desktop versions of Ubuntu.

**Alan F** · August 6th, 2015

Originally Posted by Cavsfan

Alan F if you were able to retain 2 kernels, you would be the only one I know of. I was not able to even when the 4.0 kernels started being introduced.

I understand your scepticism and cannot understand why this has happened. This has not been manually edited.

Here is text of ..... etc/apt/apt.conf.d/01autoremove-kernels

// DO NOT EDIT! File autogenerated by /etc/kernel/postinst.d/apt-auto-removal
APT::NeverAutoRemove
{
"^linux-image-4\.1\.0-2-generic$";
"^linux-image-4\.1\.0-3-generic$";
"^linux-headers-4\.1\.0-2-generic$";
"^linux-headers-4\.1\.0-3-generic$";
"^linux-image-extra-4\.1\.0-2-generic$";
"^linux-image-extra-4\.1\.0-3-generic$";
"^linux-signed-image-4\.1\.0-2-generic$";
"^linux-signed-image-4\.1\.0-3-generic$";
"^kfreebsd-image-4\.1\.0-2-generic$";
"^kfreebsd-image-4\.1\.0-3-generic$";
"^kfreebsd-headers-4\.1\.0-2-generic$";
"^kfreebsd-headers-4\.1\.0-3-generic$";
"^gnumach-image-4\.1\.0-2-generic$";
"^gnumach-image-4\.1\.0-3-generic$";
"^.*-modules-4\.1\.0-2-generic$";
"^.*-modules-4\.1\.0-3-generic$";
"^.*-kernel-4\.1\.0-2-generic$";
"^.*-kernel-4\.1\.0-3-generic$";
"^linux-backports-modules-.*-4\.1\.0-2-generic$";
"^linux-backports-modules-.*-4\.1\.0-3-generic$";
"^linux-tools-4\.1\.0-2-generic$";
"^linux-tools-4\.1\.0-3-generic$";
};

and a screenshot of synaptic showing both kernels installed and no AutoRemove suggestions.

I await with interest the next kernel update.

**Chanath** · August 6th, 2015

I don't understand one thing. Why do you think that autoremove would remove the old kernels? Dist-upgrade might inform you that there are some older kernels, you might want to remove with autoremove, but it would never offer to remove the last kernel.