[Bug 1833556] Re: Default, encrypted install runs out of /boot space after 2 months

[Jackalux]

** Description changed:

  This bug is about the installer defaults, not this symptom of the bug.
  
- I installed a fresh install of 18.04 on a laptop with a 750GB HDD.  The
- update-manager reported that I'd ran out of space within 2 months and
- could not perform updates.
+ I installed a fresh encrypted* install of 18.04 on a laptop with a 750GB HDD.  The update-manager reported that I'd ran out of space within 2 months and could not perform updates.
+ * AFAIK, encrypted installs place /boot in a separate partition
  
  'apt autoremove' didn't remove anything and only running the advice from
  http://tuxtweaks.com/2010/10/remove-old-kernels-in-ubuntu-with-one-
  command/ worked, which seems to leave me with no backup kernel.
  
  This would turn off Noobs who want something that doesn't require almost
  immediate, then ongoing, tech intervention.
  
  Does the installer need to change the allocated size of /boot in new
  installs?  Noobs will run back to Windoze if they encounter this... it
  looks like a fresh install has a shelf life of two months unless you
  learn to fiddle around under the bonnet/hood.
  
  Blessed are the coders!
  J

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1833556

Title:
  Default, encrypted install runs out of /boot space after 2 months

Status in update-manager package in Ubuntu:
  New

Bug description:
  This bug is about the installer defaults, not this symptom of the bug.

  I installed a fresh encrypted* install of 18.04 on a laptop with a 750GB HDD.  The update-manager reported that I'd ran out of space within 2 months and could not perform updates.
  * AFAIK, encrypted installs place /boot in a separate partition

  'apt autoremove' didn't remove anything and only running the advice
  from http://tuxtweaks.com/2010/10/remove-old-kernels-in-ubuntu-with-
  one-command/ worked, which seems to leave me with no backup kernel.

  This would turn off Noobs who want something that doesn't require
  almost immediate, then ongoing, tech intervention.

  Does the installer need to change the allocated size of /boot in new
  installs?  Noobs will run back to Windoze if they encounter this... it
  looks like a fresh install has a shelf life of two months unless you
  learn to fiddle around under the bonnet/hood.

  Blessed are the coders!
  J

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1833556/+subscriptions