Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic updates #4621

Closed
DemiMarie opened this issue Dec 16, 2018 · 7 comments
Closed

Automatic updates #4621

DemiMarie opened this issue Dec 16, 2018 · 7 comments
Assignees
Labels
C: updates P: major Priority: major. Between "default" and "critical" in severity. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience

Comments

@DemiMarie
Copy link

Qubes OS version:

R4.0

Affected component(s):

Qubes update system


Steps to reproduce the behavior:

Wait for updates to be available for any Qubes template, or for dom0

Expected behavior:

Qubes pops up an alert with options like

  • Update this VM, and prompt in the future when updates are available.
  • Update this VM, and automatically apply updates in the future. You may change this by <insert instructions>.
  • Do not update this VM (NOT RECOMMENDED).

Actual behavior:

No pop-up, and no way to enable automatic installation of updates when they become available.

General notes:

Qubes should handle updates at least as well as Windows.


Related issues:

@unman
Copy link
Member

unman commented Dec 16, 2018

I would not be in favour of unattended updates at all - users easily forget what options they set, and there are clear risks in triggering them. (But then I dont favour automatic update checking either.)
If this were adopted, then I would suggest a clear visual indicator to the user that automatic updates are enabled.

@DemiMarie
Copy link
Author

@unman I absolutely agree with the clear visual indicator.

@andrewdavidwong
Copy link
Member

Duplicate of #2718

@andrewdavidwong andrewdavidwong marked this as a duplicate of #2718 Dec 17, 2018
@andrewdavidwong
Copy link
Member

andrewdavidwong commented Dec 17, 2018

@DemiMarie, FYI, you previously filed a very a similar issue: #4282.

Like that one, this is a duplicate of #2718.

@andrewdavidwong
Copy link
Member

This appears to be a duplicate of an existing issue. If so, please comment on the appropriate existing issue instead. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

@andrewdavidwong andrewdavidwong added the R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. label Dec 17, 2018
@andrewdavidwong andrewdavidwong marked this as not a duplicate of #2718 Dec 17, 2018
@andrewdavidwong
Copy link
Member

andrewdavidwong commented Dec 17, 2018

Reopening as a feature request for a GUI frontend for the cron functionality described in #2718 (comment):

We have a CLI way to update VMs (which can be added to cron)

@andrewdavidwong andrewdavidwong added T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. C: manager/widget ux User experience and removed R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. labels Dec 17, 2018
@andrewdavidwong andrewdavidwong added this to the Release 4.1 milestone Dec 17, 2018
@andrewdavidwong andrewdavidwong added C: updates P: major Priority: major. Between "default" and "critical" in severity. and removed C: manager/widget labels May 22, 2021
@andrewdavidwong
Copy link
Member

Actually, I no longer believe that this is a duplicate of #2718, since automatic updates are not the same as a tool for performing multiple updates at the same time. Moreover, a GUI frontend for cron functionality is also not the same as automatic updates.

Instead, I now think this is a duplicate of #4282, which I no longer believe to be a duplicate of #2718.

@andrewdavidwong andrewdavidwong added the R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. label May 22, 2021
@andrewdavidwong andrewdavidwong removed this from the Release 4.1 milestone Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: updates P: major Priority: major. Between "default" and "critical" in severity. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience
Projects
None yet
Development

No branches or pull requests

4 participants