Skip to content
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.

Do not check for updates if a reboot is required from previous update run #17

Open
eloquence opened this issue Feb 15, 2020 · 3 comments

Comments

@eloquence
Copy link
Member

eloquence commented Feb 15, 2020

Currently, if the user starts the updater a second time, and reboots are required, it will happily run through the whole "checking for updates" process again before letting the user know that they have to reboot. Instead, we should immediately alert the user that a reboot is required to apply available updates.

The screen for successful updates that require a reboot currently looks like this:

[====100%====]
All updates complete!
A reboot is required for security updates to be applied.
Please click the Reboot button to continue.
[Reboot]

I think if the user launches the updater again now without having rebooted, it should immediately show a screen similar to the above, with two differences:

  • omit the progress bar
  • instead of "All updates complete", say something like "One more step" or omit the text (can kick this around a bit on this issue).
@eloquence
Copy link
Member Author

(First noted here.)

@eloquence
Copy link
Member Author

Tracking as stretch goal since it's an annoying waste of the user's time in a secondary path. The "happy path" is that the user immediately requests a reboot.

@zenmonkeykstop
Copy link
Contributor

This should be obsoleted by coming changes in the Qubes Updater, will close it then.

@zenmonkeykstop zenmonkeykstop transferred this issue from freedomofpress/securedrop-workstation Feb 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants