I had managed to get it working the last couple of times I set up Qubes but this time I run into a problem which prevented me from installing it at all.
[user@dom0 Desktop]$ redshift
bash: redshift: command not found
[user@dom0 Desktop]$ sudo qubes-dom0-update redshift
Using sys-whonix as UpdateVM for Dom0
Downloading packages. This may take a while...
Unable to detect release version (use '--releasever' to specify release version)
Unable to detect release version (use '--releasever' to specify release version)
Unable to detect release version (use '--releasever' to specify release version)
Fedora 37 - x86_64 129 kB/s | 70 MB 09:16
Fedora 37 - x86_64 - Updates 244 kB/s | 43 MB 03:01
Qubes Host Repository (updates) 184 kB/s | 3.7 MB 00:20
Last metadata expiration check: 0:00:14 ago on Sun Dec 22 17:45:39 2024.
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Installing:
redshift x86_64 1.12-16.fc37 fedora 162 k
Installing dependencies:
ModemManager-glib x86_64 1.18.12-1.fc37 updates 301 k
geoclue2 x86_64 2.6.0-3.fc37 fedora 144 k
Transaction Summary
================================================================================
Install 3 Packages
Total download size: 607 k
Installed size: 2.3 M
DNF will only download packages for the transaction.
Downloading Packages:
(1/3): geoclue2-2.6.0-3.fc37.x86_64.rpm 70 kB/s | 144 kB 00:02
(2/3): redshift-1.12-16.fc37.x86_64.rpm 65 kB/s | 162 kB 00:02
(3/3): ModemManager-glib-1.18.12-1.fc37.x86_64. 64 kB/s | 301 kB 00:04
--------------------------------------------------------------------------------
Total 91 kB/s | 607 kB 00:06
Complete!
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Last metadata expiration check: -1 day, 22:19:00 ago on Sun 22 Dec 2024 07:27:05 PM UTC.
No match for argument: redshift
Error: Unable to find a match: redshift
[user@dom0 Desktop]$ redshift
bash: redshift: command not found
/usr/bin/reshift is provided by package redshift, it seems you should have it installed, the output only say it was downloaded, but there is nothing about installation.
Does this command output something? dnf list --installed | grep redshift
If you want a GUI for redshift, you will want to install redshift-gtk, otherwise redshift is command line only.
Maybe sys-whonix downloading packages create issues? qubes-dom0-update output looks like this for me when trying to install a package.
[root@dom0 ~]# qubes-dom0-update mercurial
Using sys-firewall as UpdateVM for Dom0
Downloading packages. This may take a while...
Fedora 37 - x86_64 14 kB/s | 5.5 kB 00:00
Fedora 37 - x86_64 - Updates 17 kB/s | 5.4 kB 00:00
Qubes Host Repository (updates) 23 kB/s | 2.7 kB 00:00
Qubes Host Repository (updates-testing) 25 kB/s | 2.8 kB 00:00
Qubes Host Repository (security-testing) 24 kB/s | 2.8 kB 00:00
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Installing:
mercurial x86_64 6.2.3-2.fc37 updates 6.4 M
Installing dependencies:
re2 x86_64 1:20220601-1.fc37 updates 194 k
Installing weak dependencies:
python3-fb-re2 x86_64 1.0.7-10.fc37 fedora 24 k
Transaction Summary
================================================================================
Install 3 Packages
Total download size: 6.6 M
Installed size: 31 M
DNF will only download packages for the transaction.
Downloading Packages:
(1/3): re2-20220601-1.fc37.x86_64.rpm 648 kB/s | 194 kB 00:00
(2/3): mercurial-6.2.3-2.fc37.x86_64.rpm 11 MB/s | 6.4 MB 00:00
(3/3): python3-fb-re2-1.0.7-10.fc37.x86_64.rpm 27 kB/s | 24 kB 00:00
--------------------------------------------------------------------------------
Total 3.7 MB/s | 6.6 MB 00:01
Complete!
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00
Qubes OS Repository for Dom0 197 kB/s | 11 kB 00:00
Dépendances résolues.
==============================================================================================================================================================================================
Paquet Architecture Version Dépôt Taille
==============================================================================================================================================================================================
Installation:
mercurial x86_64 6.2.3-2.fc37 qubes-dom0-cached 6.1 M
Installation des dépendances:
re2 x86_64 1:20220601-1.fc37 qubes-dom0-cached 191 k
Installation des dépendances faibles:
python3-fb-re2 x86_64 1.0.7-10.fc37 qubes-dom0-cached 20 k
Résumé de la transaction
==============================================================================================================================================================================================
Installer 3 Paquets
Taille totale : 6.3 M
Taille des paquets installés : 31 M
Voulez-vous continuer ? [o/N] : n
Opération avortée.
So if sys-whonix is what’s causing issues, how do I fix it?
It worked perfectly fine for me before and I want to stick with using sys-whonix for my updates.
Otherwise, how can I switch to sys-firewall for updates, at least temporarily?
From “Qubes Global Config” GUI in the “Updates” tab, switch to sys-firewall for instance, try to install redshift, and put sys-whonix back whenever you want.
Unable to detect release version (use '--releasever' to specify release version)
Unable to detect release version (use '--releasever' to specify release version)
Unable to detect release version (use '--releasever' to specify release version)
and the fact it doesn’t ask you if you want to install it once it’s downloaded… weird
if you want to download updates through Tor, maybe just add disposable qube with sys-whonix as a netvm, and use it for updates. I know sys-whonix is picky about many things actually
I, too, get always the same warning/error… even when specifying the “realeasever”
And the dom0 update works anyway.
[user@dom0 ~]$ sudo qubes-dom0-update --releasever=4.2
Using sys-whonix as UpdateVM for Dom0
Downloading updates. This may take a while...
Unable to detect release version (use '--releasever' to specify release version)
Unable to detect release version (use '--releasever' to specify release version)
Unable to detect release version (use '--releasever' to specify release version)
Fedora 37 - x86_64 2.6 MB/s | 70 MB 00:24
Fedora 37 - x86_64 - Updates 2.9 MB/s | 43 MB 00:18
Qubes Host Repository (updates) 892 kB/s | 3.7 MB 00:04
Last metadata expiration check: 0:00:04 ago on Mon Dec 23 11:49:49 2024.
Dependencies resolved.
Nothing to do.
Complete!
No packages downloaded
Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00
[user@dom0 ~]$
Started to behave this way back when R4.1 was still supported.
