Closed Bug 624813 Opened 14 years ago Closed 10 years ago

app.update.lastUpdateTime.* preference can get accidentally set to a time in the future which will prevent timer notifications

Categories

(Toolkit :: Application Update, defect)

Product:
Toolkit
Component:
Application Update
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
blocking2.0 --- -

People

(Reporter: robert.strong.bugs, Unassigned)

References

Details

If a system's clock is set to a date / time in the future and the update timer manager notifies a consumer the consumer's next notification time will be based on the system's date / time. So, if the user then fixes their systems clock the next notification won't happen until after the date / time the system was set to in the future.

The update timer manager has always been this way so this is not a regression though I think this should be considered for blocking.
blocking2.0: --- → ?
Sucks but as it's not a regression and it probably only affects a small subset of users we shouldn't block the release on this
blocking2.0: ? → -
This was fixed in other bugs which I don't have the number handy for so resolving wfm
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.