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

No dom0 update notification even when updates are available #2677

Closed
andrewdavidwong opened this Issue Mar 6, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@andrewdavidwong
Member

andrewdavidwong commented Mar 6, 2017

Qubes OS version (e.g., R3.2):

R3.2


This is the opposite of #2086 (which is now fixed for me). No dom0 update notification appears in Qubes Manager even after manually running sudo qubes-dom0-update --clean --check-only and seeing that updates are indeed available.

This is arguably much worse than #2086, since users could miss important security updates this way.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 7, 2017

Member

Cannot reproduce. Check if you have (empty) file /var/lib/qubes/updates/dom0-updates-available and what owner/mode.

Member

marmarek commented Mar 7, 2017

Cannot reproduce. Check if you have (empty) file /var/lib/qubes/updates/dom0-updates-available and what owner/mode.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 7, 2017

Member

Cannot reproduce.

Strange. I could reproduce it on two different Qubes machines.

Check if you have (empty) file /var/lib/qubes/updates/dom0-updates-available and what owner/mode.

I have no such file (but also no available updates right now, FWIW).

Member

andrewdavidwong commented Mar 7, 2017

Cannot reproduce.

Strange. I could reproduce it on two different Qubes machines.

Check if you have (empty) file /var/lib/qubes/updates/dom0-updates-available and what owner/mode.

I have no such file (but also no available updates right now, FWIW).

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 7, 2017

Member

What about directory, especially it's mode? Should be owned by group qubes and group writable.

Member

marmarek commented Mar 7, 2017

What about directory, especially it's mode? Should be owned by group qubes and group writable.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 7, 2017

Member

What about directory, especially it's mode? Should be owned by group qubes and group writable.

drwxrwx---  4 root qubes [...] updates/
Member

andrewdavidwong commented Mar 7, 2017

What about directory, especially it's mode? Should be owned by group qubes and group writable.

drwxrwx---  4 root qubes [...] updates/
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 7, 2017

Member

That notification flag is not created by qubes-dom0-update itself, but by a cron job started once a day (/etc/cron.daily/qubes-dom0-updates.cron). And it can be disabled in Qubes Manager in global settings.

Member

marmarek commented Mar 7, 2017

That notification flag is not created by qubes-dom0-update itself, but by a cron job started once a day (/etc/cron.daily/qubes-dom0-updates.cron). And it can be disabled in Qubes Manager in global settings.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 8, 2017

Member

I have it enabled in QM's global settings. Perhaps the cron job hadn't had a chance to run yet. I'll close this for now.

Member

andrewdavidwong commented Mar 8, 2017

I have it enabled in QM's global settings. Perhaps the cron job hadn't had a chance to run yet. I'll close this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment