| 2015-07-23 08:54:25 |
Stuart Bishop |
bug |
|
|
added bug |
| 2015-07-23 12:59:28 |
Launchpad Janitor |
update-manager (Ubuntu): status |
New |
Confirmed |
|
| 2015-08-02 17:34:20 |
Alberto Salvia Novella |
update-manager (Ubuntu): status |
Confirmed |
Won't Fix |
|
| 2017-08-03 00:08:24 |
Steve Langasek |
update-manager (Ubuntu): status |
Won't Fix |
Triaged |
|
| 2017-08-04 17:18:09 |
Brian Murray |
tags |
amd64 apport-bug third-party-packages vivid |
amd64 apport-bug rls-aa-incoming third-party-packages vivid |
|
| 2017-08-17 15:27:17 |
Brian Murray |
tags |
amd64 apport-bug rls-aa-incoming third-party-packages vivid |
amd64 apport-bug third-party-packages vivid |
|
| 2017-08-17 15:27:26 |
Brian Murray |
update-manager (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-08-17 15:28:02 |
Brian Murray |
nominated for series |
|
Ubuntu Artful |
|
| 2017-08-17 15:28:02 |
Brian Murray |
bug task added |
|
update-manager (Ubuntu Artful) |
|
| 2017-09-19 20:05:36 |
Brian Murray |
summary |
Incorrect instructions leave automatic updates blocked |
Incorrect instructions leave automatic updates blocked when /boot is full |
|
| 2017-09-20 12:22:23 |
Jarno Suni |
bug |
|
|
added subscriber Jarno Suni |
| 2017-09-20 14:49:41 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2017-09-20 19:34:36 |
Launchpad Janitor |
branch linked |
|
lp:update-manager |
|
| 2017-09-20 20:34:33 |
Brian Murray |
description |
What happens:
Default installations regularly fail package updates when /boot fills up. While the ultimate cause of this bug lies elsewhere, update-manager gives the user incorrect instructions when the failure occurs:
"Not enough free disk space The upgrade needs a total of 104 M free space on disk '/boot'. Please free at least an additional 85.6 M of disk space on '/boot'. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'."
These instructions do not work, and software updates from this point on fail. The user is left vulnerable, unless they have knowledgeable assistance or are technically capable enough to research and fix the problem themselves.
What should happen:
update-manager should provide valid instructions for dealing with this well known problem, or better yet perform the operation itself. It is responsible for keeping the users machine up to date, and needs to handle this and similar failures.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: update-manager 1:15.04.7
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 23 15:35:46 2015
GsettingsChanges:
b'com.ubuntu.update-manager' b'show-details' b'true'
b'com.ubuntu.update-manager' b'window-height' b'706'
b'com.ubuntu.update-manager' b'first-run' b'false'
b'com.ubuntu.update-manager' b'window-width' b'701'
b'com.ubuntu.update-manager' b'launch-time' b'1437636623'
InstallationDate: Installed on 2015-03-13 (131 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: Upgraded to vivid on 2015-03-16 (128 days ago) |
[Impact]
A system's /boot mount point can fill up for many reasons and update-manager's free space check will cause update-manager to exit. A generic error message is presented which does not provide specific information to remedy the situation and subsequently can leave systems insecure.
[Test Case]
1) Create a file to be used as a /boot partition (dd if=/dev/zero of=fake-boot bs=1024 count=204800)
2) mkfs -t ext3 fake-boot
3) copy your real /boot somewhere
4) sudo mount -t ext3 fake-boot /boot
5) copy the files from step 3 to /boot
6) fill up /boot so there is less 60MB free space
7) run update-manager
8) Click "Install Now"
With the current version of update-manager you'll see an error message with instructions to "empty your trash and remove temporary packages." With the version of update-manager in -proposed you'll receive a message regarding using "sudo apt autoremove".
[Regression Potential]
We are just changing the strings used in the error message, which will introduce untranslated strings but that is better than leaving people with systems that cannot update.
Original Description
--------------------
What happens:
Default installations regularly fail package updates when /boot fills up. While the ultimate cause of this bug lies elsewhere, update-manager gives the user incorrect instructions when the failure occurs:
"Not enough free disk space The upgrade needs a total of 104 M free space on disk '/boot'. Please free at least an additional 85.6 M of disk space on '/boot'. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'."
These instructions do not work, and software updates from this point on fail. The user is left vulnerable, unless they have knowledgeable assistance or are technically capable enough to research and fix the problem themselves.
What should happen:
update-manager should provide valid instructions for dealing with this well known problem, or better yet perform the operation itself. It is responsible for keeping the users machine up to date, and needs to handle this and similar failures.
ProblemType: BugDistroRelease: Ubuntu 15.04
Package: update-manager 1:15.04.7
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 23 15:35:46 2015
GsettingsChanges:
b'com.ubuntu.update-manager' b'show-details' b'true'
b'com.ubuntu.update-manager' b'window-height' b'706'
b'com.ubuntu.update-manager' b'first-run' b'false'
b'com.ubuntu.update-manager' b'window-width' b'701'
b'com.ubuntu.update-manager' b'launch-time' b'1437636623'
InstallationDate: Installed on 2015-03-13 (131 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: allSourcePackage: update-manager
UpgradeStatus: Upgraded to vivid on 2015-03-16 (128 days ago) |
|
| 2017-09-20 20:35:01 |
Brian Murray |
description |
[Impact]
A system's /boot mount point can fill up for many reasons and update-manager's free space check will cause update-manager to exit. A generic error message is presented which does not provide specific information to remedy the situation and subsequently can leave systems insecure.
[Test Case]
1) Create a file to be used as a /boot partition (dd if=/dev/zero of=fake-boot bs=1024 count=204800)
2) mkfs -t ext3 fake-boot
3) copy your real /boot somewhere
4) sudo mount -t ext3 fake-boot /boot
5) copy the files from step 3 to /boot
6) fill up /boot so there is less 60MB free space
7) run update-manager
8) Click "Install Now"
With the current version of update-manager you'll see an error message with instructions to "empty your trash and remove temporary packages." With the version of update-manager in -proposed you'll receive a message regarding using "sudo apt autoremove".
[Regression Potential]
We are just changing the strings used in the error message, which will introduce untranslated strings but that is better than leaving people with systems that cannot update.
Original Description
--------------------
What happens:
Default installations regularly fail package updates when /boot fills up. While the ultimate cause of this bug lies elsewhere, update-manager gives the user incorrect instructions when the failure occurs:
"Not enough free disk space The upgrade needs a total of 104 M free space on disk '/boot'. Please free at least an additional 85.6 M of disk space on '/boot'. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'."
These instructions do not work, and software updates from this point on fail. The user is left vulnerable, unless they have knowledgeable assistance or are technically capable enough to research and fix the problem themselves.
What should happen:
update-manager should provide valid instructions for dealing with this well known problem, or better yet perform the operation itself. It is responsible for keeping the users machine up to date, and needs to handle this and similar failures.
ProblemType: BugDistroRelease: Ubuntu 15.04
Package: update-manager 1:15.04.7
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 23 15:35:46 2015
GsettingsChanges:
b'com.ubuntu.update-manager' b'show-details' b'true'
b'com.ubuntu.update-manager' b'window-height' b'706'
b'com.ubuntu.update-manager' b'first-run' b'false'
b'com.ubuntu.update-manager' b'window-width' b'701'
b'com.ubuntu.update-manager' b'launch-time' b'1437636623'
InstallationDate: Installed on 2015-03-13 (131 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: allSourcePackage: update-manager
UpgradeStatus: Upgraded to vivid on 2015-03-16 (128 days ago) |
[Impact]
A system's /boot mount point can fill up for many reasons and update-manager's free space check will cause update-manager to exit. A generic error message is presented which does not provide specific information to remedy the situation and subsequently can leave systems insecure.
[Test Case]
0) Ensure your system does not have the latest kernel installed
1) Create a file to be used as a /boot partition (dd if=/dev/zero of=fake-boot bs=1024 count=204800)
2) mkfs -t ext3 fake-boot
3) copy your real /boot somewhere
4) sudo mount -t ext3 fake-boot /boot
5) copy the files from step 3 to /boot
6) fill up /boot so there is less 60MB free space
7) run update-manager
8) Click "Install Now"
With the current version of update-manager you'll see an error message with instructions to "empty your trash and remove temporary packages." With the version of update-manager in -proposed you'll receive a message regarding using "sudo apt autoremove".
[Regression Potential]
We are just changing the strings used in the error message, which will introduce untranslated strings but that is better than leaving people with systems that cannot update.
Original Description
--------------------
What happens:
Default installations regularly fail package updates when /boot fills up. While the ultimate cause of this bug lies elsewhere, update-manager gives the user incorrect instructions when the failure occurs:
"Not enough free disk space The upgrade needs a total of 104 M free space on disk '/boot'. Please free at least an additional 85.6 M of disk space on '/boot'. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'."
These instructions do not work, and software updates from this point on fail. The user is left vulnerable, unless they have knowledgeable assistance or are technically capable enough to research and fix the problem themselves.
What should happen:
update-manager should provide valid instructions for dealing with this well known problem, or better yet perform the operation itself. It is responsible for keeping the users machine up to date, and needs to handle this and similar failures.
ProblemType: BugDistroRelease: Ubuntu 15.04
Package: update-manager 1:15.04.7
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 23 15:35:46 2015
GsettingsChanges:
b'com.ubuntu.update-manager' b'show-details' b'true'
b'com.ubuntu.update-manager' b'window-height' b'706'
b'com.ubuntu.update-manager' b'first-run' b'false'
b'com.ubuntu.update-manager' b'window-width' b'701'
b'com.ubuntu.update-manager' b'launch-time' b'1437636623'
InstallationDate: Installed on 2015-03-13 (131 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: allSourcePackage: update-manager
UpgradeStatus: Upgraded to vivid on 2015-03-16 (128 days ago) |
|
| 2017-09-20 21:23:02 |
Launchpad Janitor |
update-manager (Ubuntu Artful): status |
Triaged |
Fix Released |
|
| 2017-09-20 21:42:27 |
Brian Murray |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-09-20 21:42:27 |
Brian Murray |
bug task added |
|
update-manager (Ubuntu Xenial) |
|
| 2017-09-20 21:42:27 |
Brian Murray |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-09-20 21:42:27 |
Brian Murray |
bug task added |
|
update-manager (Ubuntu Zesty) |
|
| 2017-09-20 21:42:35 |
Brian Murray |
update-manager (Ubuntu Xenial): status |
New |
In Progress |
|
| 2017-09-20 21:42:38 |
Brian Murray |
update-manager (Ubuntu Zesty): status |
New |
In Progress |
|
| 2017-09-20 21:42:41 |
Brian Murray |
update-manager (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2017-09-20 21:42:44 |
Brian Murray |
update-manager (Ubuntu Zesty): importance |
Undecided |
Medium |
|
| 2017-09-20 21:42:46 |
Brian Murray |
update-manager (Ubuntu Xenial): assignee |
|
Brian Murray (brian-murray) |
|
| 2017-09-20 21:42:48 |
Brian Murray |
update-manager (Ubuntu Zesty): assignee |
|
Brian Murray (brian-murray) |
|
| 2017-09-29 17:32:08 |
Francis Ginther |
tags |
amd64 apport-bug third-party-packages vivid |
amd64 apport-bug id-5982561eb1d9aa0d07be953f third-party-packages vivid |
|
| 2017-09-29 17:32:19 |
Francis Ginther |
tags |
amd64 apport-bug id-5982561eb1d9aa0d07be953f third-party-packages vivid |
amd64 apport-bug id-5982561eb1d9aa0d07be953f id-59c2cd399a13d92db1cb4711 third-party-packages vivid |
|
| 2017-10-03 17:07:41 |
Brian Murray |
bug |
|
|
added subscriber Matthew Paul Thomas |
| 2017-10-17 21:19:32 |
Brian Murray |
update-manager (Ubuntu Zesty): status |
In Progress |
Fix Committed |
|
| 2017-10-17 21:19:35 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-10-17 21:19:38 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-10-17 21:19:43 |
Brian Murray |
tags |
amd64 apport-bug id-5982561eb1d9aa0d07be953f id-59c2cd399a13d92db1cb4711 third-party-packages vivid |
amd64 apport-bug id-5982561eb1d9aa0d07be953f id-59c2cd399a13d92db1cb4711 third-party-packages verification-needed verification-needed-zesty vivid |
|
| 2017-10-17 21:24:11 |
Brian Murray |
update-manager (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-10-17 21:24:19 |
Brian Murray |
tags |
amd64 apport-bug id-5982561eb1d9aa0d07be953f id-59c2cd399a13d92db1cb4711 third-party-packages verification-needed verification-needed-zesty vivid |
amd64 apport-bug id-5982561eb1d9aa0d07be953f id-59c2cd399a13d92db1cb4711 third-party-packages verification-needed verification-needed-xenial verification-needed-zesty vivid |
|
| 2017-10-30 21:32:25 |
Brian Murray |
tags |
amd64 apport-bug id-5982561eb1d9aa0d07be953f id-59c2cd399a13d92db1cb4711 third-party-packages verification-needed verification-needed-xenial verification-needed-zesty vivid |
amd64 apport-bug id-5982561eb1d9aa0d07be953f id-59c2cd399a13d92db1cb4711 third-party-packages verification-done-zesty verification-needed verification-needed-xenial vivid |
|
| 2017-10-30 21:51:11 |
Brian Murray |
tags |
amd64 apport-bug id-5982561eb1d9aa0d07be953f id-59c2cd399a13d92db1cb4711 third-party-packages verification-done-zesty verification-needed verification-needed-xenial vivid |
amd64 apport-bug id-5982561eb1d9aa0d07be953f id-59c2cd399a13d92db1cb4711 third-party-packages verification-done-xenial verification-done-zesty verification-needed vivid |
|
| 2017-10-31 17:06:22 |
Launchpad Janitor |
update-manager (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-10-31 17:06:29 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-10-31 17:06:48 |
Launchpad Janitor |
update-manager (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
