Some thoughts on this bug: When /boot does run out of space, it causes the next install of a kernel package to fail, leaving the package in a broken state as far as apt is concerned. That makes it impossible to remove the old kernel packages using apt: apt won't remove packages until you successfully run apt-get -f install to fix broken packages but apt-get -f install won't run until you remove the old packages.
That means that the only way to get things working again is to manually remove some old files from /boot, then run apt-get -f install and then apt-get remove to remove the old kernel packages. That's a real pain for a technical user like myself but it's impossible for a non-technical user. This bug might not be a security vulnerability in its own right but it can certainly compound other security vulnerabilities. Being stuck with an unpatched kernel even though you have a cron job that does a sudo apt-get upgrade every night could be a big problem. I suspect that more users will be affected by this bug but the lack of a clear error probably means that non-technical users just give up or ignore it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037285 Title: /boot fills up after many kernel upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1037285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
