Hi Team
A while ago, I did setup Proton VPN: sys-vpn-protonvpn-app with this installation way:
Link: ProtonVPN App 4.2 setup guide
Link (Proton VPN): How to install Proton VPN on Fedora | Proton VPN
Few days ago, I got that message in the main notification: “The following qubes are based on distributions that are no longer supported”. So it says, that I should install new templates with Template Manger.
Why does this happens? Maybe of the old Fedora 40 version? What is the best way to do? Just change the template or rather a new dedicated Qube creation with the Standalone (StandaloneVM) type?
1 Like
unman
May 17, 2025, 11:18am
3
Few days ago, I got that message in the main notification: “The following qubes are based on distributions that are no longer supported”. So it says, that I should install new templates with Template Manger.
You can upgrade the template in place, or you can install a newcan use a standalone, but you will lose the advantages of using a
I did an in place upgrade of the fedora-40-xfce and renamed it to fedora-xfce-41, but the error persist. any way to reset the alert?
Sincerely
1 Like
The in-place upgrade should have updated the flags (as seen in qvm-features YOURTEMPLATE in the EOL and template fields), which you could set on your own but I wouldn’t advise.
out of curiosity/stubbornness, I’m trying the gui Template Manager again - it seems to be downloading now, fingers crossed.
I don’t understand the names its using, and how it distinguishes between my erroneous 41 (‘40-41’) and the real. See the image below - is the 2024 fedora-41-xfce listed as “installed” actually my ‘erroneous-40-41’, i.e. really fedora-40-xfce, OR a previous version of fedora-41-xfce that is now obsolete? (I note that the version number of fedora-40-xfce is different).
[Qu…
1 Like
unman
May 19, 2025, 1:36am
6
I dont see an issue with resetting the values with qvm-features
1 Like
Say a user sets the “EOL” to 2029… Not ideal. Also (edit, which @unman won’t see since they only use email posting), setting to an arbitrary date is mostly what I meant by changing the qvm-features warning:
opened 09:42AM - 23 Nov 23 UTC
closed 11:23PM - 23 Jun 24 UTC
C: manager/widget
C: doc
P: critical
diagnosed
pr submitted
C: updates
r4.2-vm-fc37-stable
r4.2-vm-bookworm-stable
r4.2-host-stable
r4.2-vm-fc38-stable
affects-4.2
r4.2-vm-fc39-stable
r4.2-vm-trixie-stable
r4.2-vm-fc40-stable
r4.3-vm-bookworm-cur-test
r4.3-vm-trixie-cur-test
r4.3-vm-fc39-cur-test
r4.3-vm-fc40-cur-test
### Qubes OS release
4.2-rc4
### Brief summary
The new Qubes Updater … introduced [a new way](https://github.com/QubesOS/qubes-desktop-linux-manager/blob/main/qui/utils.py#L83-L95) to detect if a template or standalone qube is no longer supported.
It works, but shows false positives for users who use the in-place upgrade method for their qubes.
The "template-name" option in qvm-features retains its old value and Qubes Updater uses it to check if the system is EOL.
### Steps to reproduce
Not really reproducible by itself, since it only happens to users who upgrade their templates/standalone qubes in-place.
Can be artificially reproduced by changing the `template-name` value to an old template version:
- `qvm-features fedora-38-xxx template-name fedora-35`
### Expected behavior
No "no longer supported" message should appear in Qubes Updater qui if the qube runs a supported release.
### Actual behavior
Say that some of my qubes are no longer supported (reported as "obsolete" in Qubes Updater itself) when they are fully upgraded to fedora-38.
Running qvm-features on one of the affected template reports the following:
```
template-name fedora-35
template-epoch 0
template-version 4.0.6
template-release 202111131804
template-reponame qubes-templates-itl-testing
template-buildtime 2021-11-13 19:14:50
template-installtime 2021-12-07 18:11:25
template-license GPL
template-url http://www.qubes-os.org
template-summary Qubes template for fedora-35
template-description Qubes template for fedora-35
```
3 Likes
dhimh
May 19, 2025, 9:47am
8
I had the same problem with the Proton VPN qube . After running
sudo dnf clean all
sudo dnf --releasever=41 distro-sync --best --allowerasing
in the Proton VPN qube, and restarting the qube, sudo cat /etc/fedora-release returned 41 as expected. But
qvm-features sys-vpn-protonvpn-app
still returned os-version 40 and os-eol 2025-05-13.
The following command from this issue comment solved it for me:
qvm-run -u root --service sys-vpn-protonvpn-app qubes.PostInstall
Thanks @kenosen for mentioning this issue!
2 Likes