[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock"
We decided this is not a release blocker as actually, what I missed mentioning earlier, this does not cause actually the installation to fail (the title was wrong). The install still finishes but at the end the user is presented with an error message that the refresh of installed applications failed. The message however does mention that everything is ok with the system just with the applications left in previous state and risk of them not working without a reinstall (or something similar). The system is bootable and still works. Changing description to make that clear. ** Tags added: release-dd-incoming ** Summary changed: - Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock" + Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock" ** Description changed: When trying to reinstall an existing Ubuntu cosmic installation using - latest 18.10 desktop images, the install fails around the end of the - installation with an "Error restoring installed applications". Looking - at the syslog such a traceback can be seen: + latest 18.10 desktop images, the install shows an error dialog around + the end of the installation with an "Error restoring installed + applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: - * Download latest cosmic image - * Install cosmic on the whole disk (can be on a VM) - * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) - * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu - * Finish configuration + * Download latest cosmic image + * Install cosmic on the whole disk (can be on a VM) + * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) + * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu + * Finish configuration - The install will fail around the end of the installation process. + The install itself doesn't fail, but around the end of the installation + process the error dialog appears. System is still bootable but left with + old packages. ** Changed in: apt (Ubuntu) Status: Confirmed => Invalid ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1798369 Title: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install shows an error dialog around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install itself doesn't fail, but around the end of the installation process the error dialog appears. System is still bootable but left with old packages. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock"
I installed cosmic in a KVM vm using virt-manager, then ran update- manager to update a few packages leaving the lock file behind, restarted to the installer, chose reinstall and the installer is stuck in systemd[1]: Started Cleanup of Temporary Directories. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1798369 Title: Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Confirmed Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install fails around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install will fail around the end of the installation process. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock"
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1798369 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1798369 Title: Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Confirmed Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install fails around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install will fail around the end of the installation process. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1798369 Title: Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Confirmed Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install fails around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install will fail around the end of the installation process. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock"
Also seen running 'manual partitioning' test case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1798369 Title: Reinstall Ubuntu (with preserving existing data) fails due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Confirmed Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install fails around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install will fail around the end of the installation process. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
