Details pane against unavailable Pro updates is misleading
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Fix Released
|
High
|
Nathan Teodosio | ||
Xenial |
Fix Released
|
High
|
Nathan Teodosio | ||
Bionic |
Fix Released
|
High
|
Nathan Teodosio | ||
Focal |
Fix Committed
|
High
|
Nathan Teodosio | ||
Jammy |
Fix Released
|
High
|
Nathan Teodosio | ||
Noble |
Fix Released
|
High
|
Nathan Teodosio |
Bug Description
* Impact
If Pro is not enabled, then the details pane against a Pro update misleads the user into believing that there is no update available.
Example of someone being misled: https:/
Expected results: either no details presented, or the actual details of the potential Pro update presented
Actual results: a message that implies that there is no update available for this package, Pro or not.
* Test Case
Install the update on a system not attached to Pro, select an update in the Pro section, check the 'Version available' string, it should reflect the version that would be installed if pro was enabled
* Regression potential
The change is in the code getting the available version to display, if the logic was wrong it could lead to have the 'available version' label being missing or incorrect. The code could hit an exception if there was not non expected value
Related branches
- Sebastien Bacher: Approve
-
Diff: 64 lines (+19/-2)3 files modifiedUpdateManager/Core/MyCache.py (+11/-2)
UpdateManager/UpdateManager.py (+1/-0)
debian/changelog (+7/-0)
- Sebastien Bacher: Pending requested
-
Diff: 65 lines (+20/-2)3 files modifiedUpdateManager/Core/MyCache.py (+11/-2)
UpdateManager/UpdateManager.py (+1/-0)
debian/changelog (+8/-0)
- Sebastien Bacher: Approve
-
Diff: 65 lines (+20/-2)3 files modifiedUpdateManager/Core/MyCache.py (+11/-2)
UpdateManager/UpdateManager.py (+1/-0)
debian/changelog (+8/-0)
- Sebastien Bacher: Approve
-
Diff: 67 lines (+19/-1)3 files modifiedUpdateManager/Core/MyCache.py (+11/-1)
UpdateManager/UpdateManager.py (+1/-0)
debian/changelog (+7/-0)
- Sebastien Bacher: Approve
-
Diff: 64 lines (+19/-2)3 files modifiedUpdateManager/Core/MyCache.py (+11/-2)
UpdateManager/UpdateManager.py (+1/-0)
debian/changelog (+7/-0)
description: | updated |
Changed in update-manager (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Nathan Teodosio (nteodosio) |
importance: | Undecided → High |
Changed in update-manager (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in update-manager (Ubuntu Focal): | |
status: | New → In Progress |
Changed in update-manager (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in update-manager (Ubuntu Xenial): | |
status: | New → In Progress |
assignee: | nobody → Nathan Teodosio (nteodosio) |
Changed in update-manager (Ubuntu Bionic): | |
assignee: | nobody → Nathan Teodosio (nteodosio) |
Changed in update-manager (Ubuntu Focal): | |
assignee: | nobody → Nathan Teodosio (nteodosio) |
Changed in update-manager (Ubuntu Jammy): | |
assignee: | nobody → Nathan Teodosio (nteodosio) |
importance: | Undecided → High |
Changed in update-manager (Ubuntu Focal): | |
importance: | Undecided → High |
Changed in update-manager (Ubuntu Bionic): | |
importance: | Undecided → High |
Changed in update-manager (Ubuntu Xenial): | |
importance: | Undecided → High |
description: | updated |
Indeed the UI there is confusing. When the system is not attached to Ubuntu Pro the updates are unknown to apt. We build the UI by getting a list of binaries from 'pro security-status' but we didn't include extra logic to adapt the 'details' section. The 'available' version comes from apt and in this case there is no update.
We could probably also get the version for the pro command to fix the 'available version' information but I'm unsure if we have a way to have access to the changelog to display actual content.
@Design, what would we recommend doing? Should we just fix the version even without changelog description? Hide the section? Add some text explaining how the Pro updates are different?