Unresponsive window at the end of the initial phase
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
In Progress
|
Undecided
|
Nathan Teodosio |
Bug Description
In the "first phase" of update-manager, the program updates the Apt cache and at the end of it calculates the updates for the system. The latter is done synchronously; It blocks the events in the Gtk window, including signals. That manifests itself to the end user as:
1. Inability to close the window via soft methods, such as INT or the window manager's close action. Xkill still works but leaves the process running.
2. Window stops being drawn and becomes just a passive box. E.g. when raising a window above update-manager and raising update-manager again, it just displays the contents of that other window.
That is captured in the attached video (umsl.mkv).
The operation (cache.
Related branches
- Sebastien Bacher: Approve
- Marco Trevisan (Treviño) (community): Approve
-
Diff: 384 lines (+142/-110)2 files modifiedUpdateManager/Core/UpdateList.py (+20/-25)
UpdateManager/UpdateManager.py (+122/-85)
- Marco Trevisan (Treviño) (community): Needs Fixing
- Ubuntu Core Development Team: Pending requested
-
Diff: 96 lines (+34/-10)3 files modifiedUpdateManager/Core/utils.py (+15/-0)
UpdateManager/UpdateManager.py (+13/-10)
debian/changelog (+6/-0)
description: | updated |