Last Updated column in Qubes Update GUI isn't properly updating

User Support General
,
1

Hi,

For the past several weeks, I’ve noticed that the date in the Last Updated column in the Qubes-Update-GUI has been inconsistently updating (i.e., not correctly updating), despite the fact that package updates have been successfully installed. I’m running Qubes 4.3.0, and I’ve never had this type of issue.

As an example, my fedora-43 template shows a date of 2026-03-27, although it has been receiving numerous package updates since then (based on GUI details — see example below). My fedora-43-xfce template shows 2026-03-31. I even have some minimal templates that list dates from last summer. Again, I know those dates aren’t correct, because even minimal templates have significant updates periodically and I’ve seen them occurring.

By contrast, my debian-13 and whonix-gateway-18 templates both correctly show a Last Checked and Last Updated date of yesterday. So, I’m even more puzzled.

Here’s an example of the fedora-43 log from today’s update. As you can see, no errors and updated successfully, but the Last Updated date remains unchanged. The Last Checked date is always correct for all qubes. In this case, the GUI immediately shows “today” for fedora-43.

A couple of questions for the community:

  1. Is there any way to “reset” this information to get proper information on all my templates?

  2. Has anyone else experienced this? If so, did the issue eventually self-correct, or did you specifically can some corrective action?

  3. Or is this a bug that should be reported on [GitHub - QubesOS/qubes-issues: The Qubes OS Project issue tracker · GitHub](https://Qubes github)?

Overall, it’s a minor inconvenience on an otherwise fantastic operating system. :clap: :clap: That said, I would like to fix it, if possible. Any guidance is appreciation, and thanks for reading this post.

Updating fedora-43
Refreshing package info
Removed 0 files, 0 directories (total of 0 B). 0 errors occurred.
Fetching 12 packages [195.24 MiB]
Fetching kernel-core-0:6.19.12-200.fc43.x86_64 [20.08 MiB]
Fetching kernel-modules-core-0:6.19.12-200.fc43.x86_64 [72.59 MiB]
Fetching kernel-modules-0:6.19.12-200.fc43.x86_64 [98.72 MiB]
Fetching kernel-0:6.19.12-200.fc43.x86_64 [444.93 KiB]
Fetching NetworkManager-ssh-0:1.4.4-1.fc43.x86_64 [87.88 KiB]
Fetching NetworkManager-ssh-gnome-0:1.4.4-1.fc43.x86_64 [42.89 KiB]
Fetching NetworkManager-ssh-selinux-0:1.4.4-1.fc43.x86_64 [18.20 KiB]
Fetching kernel-tools-0:6.19.12-200.fc43.x86_64 [744.49 KiB]
Fetching kernel-tools-libs-0:6.19.12-200.fc43.x86_64 [459.11 KiB]
Fetching perl-Module-CoreList-1:5.20260330-1.fc43.noarch [94.62 KiB]
Fetching perl-Module-CoreList-tools-1:5.20260330-1.fc43.noarch [18.59 KiB]
Fetching python3-perf-0:6.19.12-200.fc43.x86_64 [1.98 MiB]
Updating packages.
Installing kernel-core-0:6.19.12-200.fc43.x86_64
Running rpm scriptlet for kernel-core-0:6.19.12-200.fc43.x86_64
Installing kernel-modules-core-0:6.19.12-200.fc43.x86_64
Installing kernel-modules-0:6.19.12-200.fc43.x86_64
Running rpm scriptlet for kernel-modules-0:6.19.12-200.fc43.x86_64
Installing perl-Module-CoreList-1:5.20260330-1.fc43.noarch
Installing kernel-tools-libs-0:6.19.12-200.fc43.x86_64
Running rpm scriptlet for kernel-tools-libs-0:6.19.12-200.fc43.x86_64
Installing NetworkManager-ssh-selinux-0:1.4.4-1.fc43.x86_64
Running rpm scriptlet for NetworkManager-ssh-selinux-0:1.4.4-1.fc43.x86_64
Installing NetworkManager-ssh-0:1.4.4-1.fc43.x86_64
Installing NetworkManager-ssh-gnome-0:1.4.4-1.fc43.x86_64
Installing kernel-tools-0:6.19.12-200.fc43.x86_64
Running rpm scriptlet for filesystem-0:3.18-50.fc43.x86_64
Installing perl-Module-CoreList-tools-1:5.20260330-1.fc43.noarch
Running rpm scriptlet for filesystem-0:3.18-50.fc43.x86_64
Installing kernel-0:6.19.12-200.fc43.x86_64
Installing python3-perf-0:6.19.12-200.fc43.x86_64
Uninstalling kernel-0:6.19.9-200.fc43.x86_64
Uninstalling kernel-modules-0:6.19.9-200.fc43.x86_64
Running rpm scriptlet for kernel-modules-0:6.19.9-200.fc43.x86_64
Uninstalling perl-Module-CoreList-tools-1:5.20260308-1.fc43.noarch
Uninstalling kernel-tools-0:6.19.11-200.fc43.x86_64
Running rpm scriptlet for kernel-core-0:6.19.9-200.fc43.x86_64
Uninstalling kernel-core-0:6.19.9-200.fc43.x86_64
Uninstalling kernel-modules-core-0:6.19.9-200.fc43.x86_64
Uninstalling NetworkManager-ssh-gnome-0:1.4.2-1.fc43.x86_64
Uninstalling perl-Module-CoreList-1:5.20260308-1.fc43.noarch
Uninstalling NetworkManager-ssh-0:1.4.2-1.fc43.x86_64
Uninstalling NetworkManager-ssh-selinux-0:1.4.2-1.fc43.x86_64
Running rpm scriptlet for NetworkManager-ssh-selinux-0:1.4.2-1.fc43.x86_64
Uninstalling kernel-tools-libs-0:6.19.11-200.fc43.x86_64
Running rpm scriptlet for kernel-tools-libs-0:6.19.11-200.fc43.x86_64
Uninstalling python3-perf-0:6.19.11-200.fc43.x86_64
Running rpm scriptlet for kernel-core-0:6.19.12-200.fc43.x86_64
Running rpm scriptlet for kernel-modules-core-0:6.19.12-200.fc43.x86_64
Running rpm scriptlet for kernel-modules-0:6.19.12-200.fc43.x86_64
Running rpm scriptlet for NetworkManager-ssh-selinux-0:1.4.4-1.fc43.x86_64
Running rpm scriptlet for glibc-common-0:2.42-11.fc43.x86_64
Running rpm scriptlet for man-db-0:2.13.1-2.fc43.x86_64
Running rpm scriptlet for systemd-0:258.7-1.fc43.x86_64
Running rpm scriptlet for glibc-common-0:2.42-11.fc43.x86_64
Running rpm scriptlet for systemd-0:258.7-1.fc43.x86_64
Running rpm scriptlet for man-db-0:2.13.1-2.fc43.x86_64
Running rpm scriptlet for systemd-0:258.7-1.fc43.x86_64
Trimming qube storage. This may take some time...
/efi: 199.7 MiB (209436672 bytes) trimmed on /dev/xvda1
/rw: 0 B (0 bytes) trimmed on /dev/xvdb
/: 693.6 MiB (727269376 bytes) trimmed on /dev/mapper/dmroot
Updated
Installed packages:
None
Updated packages:
NetworkManager-ssh 1.4.2-1.fc43 -> 1.4.4-1.fc43
NetworkManager-ssh-gnome 1.4.2-1.fc43 -> 1.4.4-1.fc43
NetworkManager-ssh-selinux 1.4.2-1.fc43 -> 1.4.4-1.fc43
kernel 6.19.9-200.fc43', '6.19.10-200.fc43', '6.19.11-200.fc43 -> 6.19.10-200.fc43', '6.19.11-200.fc43', '6.19.12-200.fc43
kernel-core 6.19.9-200.fc43', '6.19.10-200.fc43', '6.19.11-200.fc43 -> 6.19.10-200.fc43', '6.19.11-200.fc43', '6.19.12-200.fc43
kernel-modules 6.19.9-200.fc43', '6.19.10-200.fc43', '6.19.11-200.fc43 -> 6.19.10-200.fc43', '6.19.11-200.fc43', '6.19.12-200.fc43
kernel-modules-core 6.19.9-200.fc43', '6.19.10-200.fc43', '6.19.11-200.fc43 -> 6.19.10-200.fc43', '6.19.11-200.fc43', '6.19.12-200.fc43
kernel-tools 6.19.11-200.fc43 -> 6.19.12-200.fc43
kernel-tools-libs 6.19.11-200.fc43 -> 6.19.12-200.fc43
perl-Module-CoreList 5.20260308-1.fc43 -> 5.20260330-1.fc43
perl-Module-CoreList-tools 5.20260308-1.fc43 -> 5.20260330-1.fc43
python3-perf 6.19.11-200.fc43 -> 6.19.12-200.fc43
Removed packages:
None
1 Like
2

The Last updated column reflects the last date for which a “scheduled” update check was performed by the template or the appVMs for that template. If you manually update the template then the update may, or may not, register in the Last updated column, depending on whether the “scheduled” update check kicks in. You can trigger the update check manually from dom0 with:

qvm-run -u root --pass-io --no-gui <template-name> 'systemctl restart qubes-update-check'
3

That’s not consistent with my personal experience. I will trying to find the docs make some test to tell you why exactly.

Edit: see post below

1 Like
4

Hi @ephile - Thanks for putting me on the right path for resolution. Several weeks ago, I disabled “automatic” updating checking for most qubes in Qubes Global Config, since I already manually ran Qubes Update almost every day anyways. Apparently, like you described, one of the side-effects was that “Last Updated” wasn’t getting updated through my manual checks for each and every template.

Today, I re-enabled the auto-checking. Several templates were immediately “fixed” with today’s date, and the other ones will probably get corrected in the next few days, although there may be a few mysterious hold-outs. Perhaps, a better column name would be “Last Scheduled Update Check” for people like myself :rofl:. Anyhow, many thanks again for your assistance and teaching me something. Have a good weekend!

5

Hi @parulin - Thank you for your willingness to help. As you can see from my response, it was more of an unintended consequence of my own actions. It’s always nice to find a painless solution. Have a good weekend.

6

I think I have the same issue. There something odd there, because at last, the name of the column is wrong.