Qubes Template Manager not loading and in-place upgrade "no longer supported"

User Support
,
1

After having updated from Qubes 4.1 to 4.2.3, I had most of my qubes still based on Fedora 37.

I tried to run the Qubes Template Manager as it requested to install the new Fedora 40 template, but whenever opening the Manager or using qvm-template list nothing would happen.

I had this issue before when sys-whonix wasn’t communicating to the internet properly and assumed it must be since sys-whonix was also based on Fedora 37 and marked as outdated.

Therefore I performed an in-place update of my Fedora 37 template qube to Fedora 40 successfully, but after updating, my Qubes system still considers that cube to be “no longer supported” similar to what is described here in this issue.

When using qvm-features fedora-40 in dom0 it says os-version “37” and os-eol “2023-12-05” even though I have updated it.

Does anyone have any idea how to fix this, as I also couldn’t find an answer (or maybe just didn’t understand) in the linked known issue.

The Template Manager also continues to not load after the in-place update of my Fedora Template Qube.

Tia

2

Did you try:

qvm-run -u root --service [TEMPLATENAME] qubes.PostInstall
3

After running this and rebooting, the Fedora 40 template issue is fixed now and it’s not considered “no longer supported” anymore! Yay!

The Qubes Template Manager still doesn’t load however and also my Qubes that used to have Firefox don’t show it in the application menu anymore. Before this, it would still show but also not start. Firefox does however still start if I start it through the terminal.

Not sure if any of these things are related at all.

Tia

EDIT: The Firefox issue was as simple as adding it to the qubes list of applications again and now it also opens. The only remaining issue is then, that the Qubes Template Updater doesn’t load.

4

Are you able to update dom0?
What’s the dom0 update ptoxy? You can check it in Qubes Global Settings → Updates tab.
Try to start Qubes Template Manager or qvm-template list and wait an hour or two for a test.

5

Hi, thanks for you reply!

I assume you wanted me to run sudo qubesctl --show-output state.sls update.qubes-dom0? → That worked (Succeeded: 4, Failed: 0, no changes needed to be made, cache cleaned and system is already up-to-date were the results).

The update proxy is sys-whonix according to the setting you mentioned.

So now qvm-template list for two hours?

Thanks

EDIT: After running

sudo qubesctl --show-output state.sls update.qubes-dom0

and

sudo qubesctl --show-output --skip-dom0 --templates state.sls update.qubes-vm

successfully in dom0 the Qubes Template Manager now loads just fine.

6

I have now restarted my system and now it seems like the Qubes Template Manager doesn’t load again.

I also have to correct myself, the dom0 update proxy is sys-whonix,but the default update proxy shown under the “Update proxy” subsection is sys-net and the whonix update proxy sys-whonix.

7

Qubes Template Manager is not caching the repository info and is downloading the entry repository info if you restart the dom0 update proxy. The repository info is big so, since you’ve using sys-whonix as dom0 update proxy, then it can take a long time to download it using Tor.
Just leave Qubes Template Manager open and wait for it to finish the download.
Also you can check if it’s downloading anything using Nyx in sys-whonix.

8

That makes sense, thank you! I’ll get back if there isn’t anything in a couple of hours but Nyx does show download traffic.

EDIT: It worked and the list showed after a while.