Update to comment 37
Issue 2) was my fault of not properly unmarking all components of the
kernel, so that some of it kept the "manual" status and prevented
removal. But once I severed all those marks, "apt autoremove" could do
it's work.
Issue 1) was reported first here:
I'm hitting two distinct errors here:
1) Accepting the updates from the GUI-notification, all my kernels over
the past months get marked as "manual" - though I have the strong
feeling, they should be automatic and only kept until superseded by jet
more updates:
root@Meerschweinchen:/boot#
danhash, please read https://help.ubuntu.com/community/RemoveOldKernels
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079
Title:
16.04 LTS Partition
At this point better to start a thread on Ubuntu forums.
https://ubuntuforums.org/forumdisplay.php?f=339
Already many similar questions and answers.
Also from live installer: Please copy & paste link to the Boot-info summary
report ( do not post report), the auto fix sometimes can create more
Forgive me if this has been asked and answered, but I was pointed here
by bug #1675079 which has affected my Ubuntu 16.04 LTS server for a very
long time. I have tried time and again to understand how to fix the
problem, and I can't figure it out. I see the bug is marked as fixed,
and there are
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
@jarnos But thank you for your attention to details.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079
Title:
16.04 LTS Partition /boot fills up with
@jarnos Most likely i forgot running /etc/kernel/postinst.d/apt-auto-removal
and -53- was still protected.
I don't have this system anymore, and I think the verification is convincing
enough to not repeat it for this bug.
--
You received this bug notification because you are a member of Ubuntu
@rbalint Why it does not remove linux-image-4.8.0-53-generic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079
Title:
16.04 LTS Partition /boot fills up
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial:
root@x-uu-lp-1260041:~# apt-mark auto linux-image-extra-4.8.0-56-generic
linux-image-extra-4.8.0-58-generic linux-image-extra-4.8.0-54-generic
linux-image-extra-4.8.0-53-generic
linux-image-extra-4.8.0-56-generic set to automatically installed.
I understand. Saying "the default is true" is a bit puzzling, but after
reading https://github.com/mvo5/unattended-upgrades/blob/master
/unattended-upgrade#L1957 , the conditional makes sense since the
default [object] is defined as "True". It also makes sense how this
works for proposed-16.04
The line is commented out, that's what the leading // characters mean.
Therefore the default is used, and the default is true.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Balint, I'm confused on your statement in the other dup bug report
(https://bugs.launchpad.net/ubuntu/+source/unattended-
upgrades/+bug/1357093/comments/129 ) that this is fixed in 18.04, but
looking at line 60 in the "50unattended-upgrades.Ubuntu" file in the
current package (1.1ubuntu1.18.04.7):
Hello Bryce, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.0 in a few hours, and then
in the -proposed repository.
Please help us by
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
** Changed in: unattended-upgrades (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079
Title:
16.04 LTS
Fixed update-manager is stuck in phasing because it triggered old bugs
like LP: #1791931 with the removals.
If you run sudo apt-get install update-manager to bypass phasing it will
remove the old kernels which are not marked manually installed.
--
You received this bug notification because you
Sorry to necro this bug but can someone clarify that as of now, a fresh
16.04 install with the defaults+LVM will *not* fill the /boot partition?
It was still happening for me as recently as a month or two ago I think.
--
You received this bug notification because you are a member of Ubuntu
Touch
This bug was fixed in the package update-manager - 1:17.10.14
---
update-manager (1:17.10.14) artful; urgency=medium
* Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
* Support package removals in install backends and really remove packages
This bug was fixed in the package update-manager - 1:16.04.13
---
update-manager (1:16.04.13) xenial; urgency=medium
* Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
* Support package removals in install backends and really remove packages
Setting to v-done for artful since I did the verification for bug
1624644.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Does this need different kind of verification for Xenial than what I did
in Bug #1624644?
** Description changed:
[Impact]
- * Update-manager and unattended-upgrades install many kernel packages during
the lifetime of a release but does not remove them automatically leading to
those
Oh, the test case seems to be same, marking verified.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079
Title:
16.04 LTS Partition /boot fills up with
Hello Bryce, or anyone else affected,
Accepted update-manager into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/update-
manager/1:17.10.14 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
On Tue, Mar 27, 2018 at 11:46 PM, Steve Langasek
wrote:
> Why does the update-manager upload include this code?:
>
> +running_kernel_version = subprocess.check_output(
> +["uname", "-r"], universal_newlines=True).rstrip()
> +
Why does the update-manager upload include this code?:
+running_kernel_version = subprocess.check_output(
+["uname", "-r"], universal_newlines=True).rstrip()
+self.running_kernel_pkgs_regexp = re.compile("(" + "|".join(
+[("^" + p + ".*" +
The same happens with update-manager.
** Description changed:
+ [Impact]
+
+ * Update-manager and unattended-upgrades install many kernel packages during
the lifetime of a release but does not remove them automatically leading to
those packages filling disk space potentially completely
This bug is linked in update-manager SRUs but does not target update-
manager (and is missing SRU information in the description). The bug as
written right now does not seem to directly affect update-manger - is
that the case?
--
You received this bug notification because you are a member of
This bug was fixed in the package unattended-upgrades - 1.0ubuntu1
---
unattended-upgrades (1.0ubuntu1) bionic; urgency=medium
* Merge from Debian unstable
- Remaining changes:
- unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu
Also please show the output of:
dpkg-query -Wf'${db:Status-Abbrev} ${Package}\n' | grep -E '
linux-(.*-)?image-[0-9]'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Could you attach logs in
/var/log/unattended-upgrades/
from such a system?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079
Title:
16.04 LTS Partition
** Tags added: full-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079
Title:
16.04 LTS Partition /boot fills up with Kernel images, gets underwear
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079
Title:
16.04 LTS Partition /boot fills up with Kernel images, gets underwear
in
It is not that old and not marked as fixed.
Do you claim that the bug happens even if no kernel updates are being
installed by Software Updater or by e.g. apt, but only by unattended-
upgrades?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Bug #1624644 is a very old one, marked as fixed, with considerable
discussion and confusion.
This bug is a clear indication that as of 16.04LTS, a bug exists with
/boot filling up. Maybe it's the same cause, maybe it's different
cause. This bug is trivial to reproduce: it happens on freshly
Is this more than just a duplicate of Bug #1624644?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079
Title:
16.04 LTS Partition /boot fills up with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
37 matches
Mail list logo