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.

Sign up for GitHub

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

Jump to bottom

4.0.1-rc2 Qubes Updater finds no updates after reporting that they are available after sys-whonix has connected to Tor #4650

Closed
jrsmiley opened this issue Dec 22, 2018 · 12 comments · Fixed by QubesOS/qubes-mgmt-salt-dom0-update#6
Closed

4.0.1-rc2 Qubes Updater finds no updates after reporting that they are available after sys-whonix has connected to Tor #4650

jrsmiley opened this issue Dec 22, 2018 · 12 comments · Fixed by QubesOS/qubes-mgmt-salt-dom0-update#6
Labels
C: mgmt P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. r4.0-dom0-stable r4.1-dom0-cur-test
Milestone
Release 4.0 updates

Comments

@jrsmiley
Copy link

Qubes OS version:

4.0.1-rc2

Affected component(s):

Qubes Updater

Steps to reproduce the behavior:

Hover mouse over gear icon at top right shows "Updates are available"
Left click the gear and select "Launch Updater"
fedora-29 shows that updates are available
Select Next
Open details window

Expected behavior:

Updates are downloaded and installed

Actual behavior:

Updater shows "SKIP (nothing to do)"

General notes:

Either the updater is falsely reporting that updates are available or the updater is not finding them

Related issues:

#4649
@jrsmiley
Copy link
Author

Qube Manager shows the "updates available" icon for fedora-29 and was able to apply and install them by selecting the template in QM and launching Update Qube from left-click dropdown.

So Qubes Update app is correctly reporting that updates are available, but doesn't find any when the updater is launched from there.

@marmarek
Copy link
Member

This is direct result of #2451 (fix on the way).

Also, you've created #4649, this one, #4651, #4652 about the same thing. Please don't.

This was referenced Dec 23, 2018
Closed
Closed
@jrsmiley
Copy link
Author

Those look like different problems in Qubes updater to me. One was about it not waiting for sys-whonix to establish a connection before proceeding with checking for updates. Another was about QM failing to open a dialog window for dom0 after launching updater from there.

There appear to be at least two different updaters: 1. the updater app and 2. update qube from QM

@jrsmiley
Copy link
Author

There was no way I would have associated #2451 with these from the description.

@jrsmiley
Copy link
Author

I'm just getting started reporting issues with 4.0.1-rc2 as I configure it as a regular use system. Would you prefer I don't report them since I may not always correctly identify one issue as being related to or the same as another?

@jrsmiley
Copy link
Author

It would save me a lot of time.

@jrsmiley
Copy link
Author

I certainly don't create separate issues for things that I see as the same as others. In other words, if I create duplicate issues, it's because they don't look like the same issue to me.

@marmarek
Copy link
Member

There was no way I would have associated #2451 with these from the description.

I certainly don't blame you for this, that was only stating the fact. BTW the fix is already in current-testing repository. Could you try installing it at least in dom0 and see if that fixes the problems? If any of those stays, I could miss-identify them as duplicates.

@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone Dec 23, 2018
@jrsmiley
Copy link
Author

This is not a duplicate of #4649. See my comments there and pls reopen it

marmarta added a commit to marmarta/qubes-desktop-linux-manager that referenced this issue Jan 24, 2019
@marmarta
Better handling of updates available for qui-updates and Qubes Update
e8571f5 
Fixed incorrect count of VMs needing an update and added a bunch of QOL
improvements that make it clearer that what checking a VM to be updated
means.
This may be related to a bunch of errors with updates being incorrectly
reported as unavailable.

references QubesOS/qubes-issues#4667
references QubesOS/qubes-issues#4650
@marmarta marmarta mentioned this issue Jan 24, 2019
Merged
@qubesos-bot qubesos-bot mentioned this issue Feb 22, 2019
Closed
@andrewdavidwong andrewdavidwong added the P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. label Mar 27, 2019
marmarek added a commit to marmarek/qubes-mgmt-salt-dom0-update that referenced this issue Nov 22, 2019
@marmarek
Re-run update status notification after the update
b13f980 
It may happen that no updates are available anymore (for example already
installed). In this case apt nor dnf run our notification hooks, so
informations about "no updates" is never send and template stays in
"updates available" state forever.

Fixes QubesOS/qubes-issues#4650
@marmarek marmarek mentioned this issue Nov 22, 2019
Merged
@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-mgmt-salt-dom0-update-4.1.2-1.fc29 has been pushed to the r4.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot qubesos-bot mentioned this issue Nov 30, 2019
Closed
marmarek added a commit to QubesOS/qubes-mgmt-salt-dom0-update that referenced this issue Mar 16, 2020
@marmarek
Re-run update status notification after the update
6e4e3b7 
It may happen that no updates are available anymore (for example already
installed). In this case apt nor dnf run our notification hooks, so
informations about "no updates" is never send and template stays in
"updates available" state forever.

Fixes QubesOS/qubes-issues#4650

(cherry picked from commit 4ae92f8)
@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-mgmt-salt-dom0-update-4.0.9-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot qubesos-bot mentioned this issue Mar 16, 2020
Closed
@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-mgmt-salt-dom0-update-4.0.9-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@unman unman mentioned this issue Jan 23, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: mgmt P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. r4.0-dom0-stable r4.1-dom0-cur-test
Projects
None yet
Milestone
Release 4.0 updates
Development

Successfully merging a pull request may close this issue.

Re-run update status notification after the update marmarek/qubes-mgmt-salt-dom0-update
4 participants
@marmarek @andrewdavidwong @qubesos-bot @jrsmiley