"Last Updated" time is confusing

Bug #1224867 reported by Alan Pope 🍺🐧🐱 🦄
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu system image
New
Undecided
Unassigned
ubuntu-system-settings
Invalid
Low
Unassigned

Bug Description

I flashed my phone cleanly yesterday 2013-09-12.
Today I thought I'd check for updates in system settings.
It checked and then came back saying:-

"No software update available
Last updated 2013-09-10 22:27:20"

Two things confuse me here:-

1) I didn't update it on the 10th, I updated on the 12th.
2) I don't really care when it was last updated, I care when I last checked for updates. I might like a version number in there perhaps, but knowing when the build was made (which I assume is what 2013-09-10 is referring to) isn't interesting to me as a user.

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :
Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

For me it shows when I flashed the build, retrying to check for an update doesn't update the time I last checked.

Changed in ubuntu-system-settings:
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks Alan, so what you are describing there are 2 bugs:

1- is an issue with ubuntu-system-image (that's the service providing the update date info)

2- is a design choice, you should probably open another bug about that (I discussed that with mpt earlier in the cycle and he said the date displayed should be the date when you installed the current image)

Revision history for this message
Sebastien Bacher (seb128) wrote :
Revision history for this message
Barry Warsaw (barry) wrote :

The "last update date" is currently defined as the mtime of /etc/system-image/channel.ini if it exists, falling back to the mtime of /etc/ubuntu-build. You're right that this won't be the time that the image was created, not when it was laid down on the device. If design thinks that the latter is a better time to use, then what I'd probably have to do in s-i is write a file that encapsulates the time just before the reboot to apply the update. Or conversely, recovery could write this file (that's probably a better idea).

I'll wait until design gives us the decision before making any changes in the client, or suggesting changes to recovery.

tags: added: client
Revision history for this message
Sebastien Bacher (seb128) wrote :

@Barry: what happened to bug #1215943, what you described seems inconsistant with what we decided there...

Changed in ubuntu-system-settings:
status: Confirmed → Invalid
importance: Undecided → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

(the "about" panel gets the right date by reading the timestamp btw)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.