Add synchronous method to determine if there are known updates
Bug #1370586 reported by
Ken VanDine
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu system image |
Fix Released
|
High
|
Barry Warsaw |
Bug Description
There are times when auto-checking of updates occurs outside of system-settings, which could add an emblem to the system-settings launcher icon indicating available updates. However, when launching system-settings we have no way of determining if there are already updates that system-image-dbus knows about before calling CheckForUpdates(). This causes a delay in toggling visibility of the updates available entry in system-settings, which shifts the UI around after start. See bug #1355803
We need a synchronous method to call when system-settings starts that returns a boolean if there are known updates, which we can use to determine visibility of the entry at start time.
Related branches
lp:~barry/ubuntu-system-image/citrain-250u1
- Ubuntu CI managed package branches: Pending requested
-
Diff: 497 lines (+84/-184)14 files modifiedNEWS.rst (+7/-0)
PKG-INFO (+1/-1)
dbus-manpage.rst (+15/-6)
debian/changelog (+9/-0)
setup.cfg (+1/-1)
system_image.egg-info/PKG-INFO (+1/-1)
system_image.egg-info/SOURCES.txt (+0/-1)
systemimage/bindings.py (+0/-98)
systemimage/dbus.py (+10/-2)
systemimage/main.py (+0/-27)
systemimage/testing/dbus.py (+3/-1)
systemimage/testing/nose.py (+0/-1)
systemimage/tests/test_dbus.py (+36/-44)
systemimage/version.txt (+1/-1)
tags: | added: client |
Changed in ubuntu-system-image: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Barry Warsaw (barry) |
milestone: | none → 2.5 |
importance: | High → Undecided |
importance: | Undecided → High |
tags: | added: rtm14 touch-2014-09-25 usability |
Changed in ubuntu-system-image: | |
status: | Triaged → In Progress |
Changed in ubuntu-system-image: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-system-image: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
See also LP: #1355803 for the UX impetus behind this request.