Recently I got some new problems related to updating my qubes. Some of these problem are new, some I not sure when started.
Debian qubes:
I stopped getting notification about new updates. When I manually force an update check, the update manager finds the newest packages and I complete the process successfully. But if I don’t check for updates, the package manager doesn’t notify me. Even this not always works right away: sometimes I have to check updates 2-3 times manually until my QubesOS sees and can fetch the updates.
Despite to the fact of the successful updates, every update log finish with this line:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Fedora qubes:
Today the package manager alerted me that a new update is available. When I applied the update, qubes updater said there are no updates and no packages are updated (and ended up with the yellow checkmark). I tried to update manually once more, and this time it fetched the updates which were out there, and the update succeeded.
The update logs on my fedora always finishing with this line:
dracut[E]: Module ‘systemd-pcrphase’ depends on module ‘tpm2-tss’, which can’t be installed
dracut[E]: Module ‘systemd-cryptsetup’ depends on module ‘crypt’, which can’t be installed
Does anyone knows the potential causes? What could be the problem here?
I noticed the same last week. Only Fedora-based templates get “updates available” notifications, including dom0.
I’ve seen debian-12-xfce, debian-minimal, and whonix -based templates exhibit the behavior described by @qubemanager : no updates notification, updates are available and installed by running the template updater (GUI or CLI, both work), and the update is ran twice, the final result being “0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.” (on 4.2.4)
@barto Yes there is a problem with the Debian-12 template update notifications, I think it started just before the 12.10 sub-release, please create an issue.
Basic workaround (see @qubemanager 's first post ) : launch Qubes Update and click in the checkbox of the debian-12 template, click on the bottom Upgrade button.
Hi @ludovic,
The teefix described on github worked for me! Good find, kudos!
So I took a random debian-12-minimal-based template and removed the " | tee…" in /usr/lib/qubes/upgrades-installed-check as described in the git issue. Powered off the template, started a qube based on that template, and 5 minutes later… boom, “Updates Available”.
Hi @renehoj ,
I’m curious, please could you check the qubes-update-check.service logs in a debian qube? Are you using the 4.2.4 Qubes-OS with stable repositories?
Five minutes after the debian qube startup, the qubes-update-check.timer, launches the qubes-update-check.service, which verifies if update are available and notifies dom0 about (un)available updates for the debian template.
So please, report here or as a comment in the above issue, the output of this command : sudo journalctl -fu qubes-update-check.service
I have same issue.
Version of my Qubes os is 4.2.4, but Debian-template don’t receive notification of update.
But Fedora-template receives notification of update, there are not issue.
Serious problem is that Whonix-template don’t receive notification of update too.
This cause of this problem is that Whonix is based on Debian.
Whonix is safely by default, if I change the setting, it is dangerous for default privacy.
Why has not this issue caused a big deal? What is solution to this issue?
Related: from yesterday (read the thread and the replies).
A workaround is described a few posts earlier in this thread (git link) and my reply.
Probably the fix will reach R4.2 “sometime in the next weeks”
