group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #46867
[Bug 2045918] Re: [SRU] Fix crash caused by updating update-manager from inside itself
This bug was fixed in the package update-manager - 1:20.04.10.20
---------------
update-manager (1:20.04.10.20) focal; urgency=medium
* d/control: Depend on ubuntu-advantage-tools >= 30~.
Fixes edge case whereby the program crashes upon an incomplete
response from ua security-status (LP: #2049785).
* The New Release dialog should take precedence over a list of updates dialog
if the latter would only show Ubuntu Pro updates in an unattached system.
(LP: #2051115).
update-manager (1:20.04.10.19) focal; urgency=medium
* Add back removed widgets to UI file to fix crash when updating
Upgrade Manager from inside itself (LP: #2045918).
-- Nathan Pratta Teodosio <nathan.teodosio@xxxxxxxxxxxxx> Mon, 22 Jan
2024 21:32:17 +0100
** Changed in: update-manager (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: update-manager (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2045918
Title:
[SRU] Fix crash caused by updating update-manager from inside itself
Status in update-manager package in Ubuntu:
Fix Released
Status in update-manager source package in Xenial:
Fix Released
Status in update-manager source package in Bionic:
Fix Released
Status in update-manager source package in Focal:
Fix Released
Status in update-manager source package in Jammy:
Fix Released
Status in update-manager source package in Mantic:
Won't Fix
Bug description:
Impact
------
LP:1990450 introduced Ubuntu Pro updates and news to update-manager,
but also a bug whereby updating update-manager itself while update-
manager is running replaces its UI files with a version incompatible
with the already running handle of update-manager, subsequently
causing a crash when the latter references an widget existing only in
the old UI file.
In other words, update-manager crashes if the user tries installing
the new update-manager release from inside itself.
Even though updates would have been installed successfully at that
point and subsequent runs of update-manager would not crash, the user
is none the wiser and is most likely left worried about his resulting
system state.
Test case
---------
1. Have the old version of Update Manager installed and the proposed
version available in the Apt database, such that, in Jammy for
example, 'apt install --dry-run --verbose-versions' would report
update-manager (1:22.04.9 => 1:22.04.19)
2. Start update-manager from a terminal.
3. Make sure 'Software Updater' is selected in the list. We don't care
about any other package for this test.
4. Click 'Install now'.
The installation must complete successfully and the view must be
automatically recalculated. Verify that the application didn't crash
(no tracebacks in the terminal window) and confirm with 'apt policy
update-manager' that the new version was indeed installed.
To note
-------
The recalculated view will not include references to Ubuntu Pro
(neither news pane nor Ubuntu Pro updates section), as it is still the
old version of the program that is running.
Regression potential
--------------------
GTK is very finicky about its *.ui files; We must look out for other
widgets failing to map or being relocated.
Original report
---------------
The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:22.04.17, the problem page at https://errors.ubuntu.com/problem/7b4facc926a743e632733dcc290e7cd5623b6eb0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2045918/+subscriptions