I created the issue :
opened 04:30PM - 12 Apr 25 UTC
P: default
### Qubes OS release
Qubes-OS : 4.2.4
Debian template : 12.10
### Brief summar… y
The debian qubes no more detect an update, so they don't notify dom0 about a debian template available upgrade.
### Steps to reproduce
1. Start a debian qube
2. Wait 5 minutes
3. Verify that a dom0 notification appears => no notification about a requested debian template upgrade
### Expected behavior
In the 3rd step, the debian qube notifes dom0 about a debian template upgrade
### Additional information
In the debian qube if I run the `apt-get -q update ; LANG=C apt-get -s upgrade` command, I see the packages with available upgrades:
```
root@test-d12:~# apt-get -q update ; LANG=C apt-get -s upgrade
Hit:1 https://deb.debian.org/debian bookworm InRelease
Get:2 https://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:3 https://deb.qubes-os.org/r4.2/vm bookworm InRelease [4,739 B]
...
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libwpe-1.0-1 libwpebackend-fdo-1.0-1 python3-daemon python3-lockfile
Use 'apt autoremove' to remove them.
The following packages have been kept back:
linux-image-amd64
The following packages will be upgraded:
gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 libjavascriptcoregtk-4.0-18 libjavascriptcoregtk-4.1-0
libqubesdb libwebkit2gtk-4.0-37 libwebkit2gtk-4.1-0 python3-qubesdb qubesdb qubesdb-vm xen-utils-guest
11 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
...
```
I think the problem appears around the 12.9 to 12.10 debian upgrade.
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.
3 Likes