[user@dom0 ~]$ qvm-template info
[Qrexec] /usr/lib/qubes/qvm-template-repo-query: line 40: dnf: command not found
ERROR: qrexec call 'qubes.TemplateSearch' failed.
[user@dom0 ~]$ sudo qvm-template info
[Qrexec] /usr/lib/qubes/qvm-template-repo-query: line 40: dnf: command not found
ERROR: qrexec call 'qubes.TemplateSearch' failed.
[user@dom0 ~]$ sudo qvm-template list -v
[Qrexec] /usr/lib/qubes/qvm-template-repo-query: line 40: dnf: command not found
ERROR: qrexec call 'qubes.TemplateSearch' failed.
2021-06-03 19:44:54,417 [MainProcess qvm_template.main:1544] app: qrexec call 'qubes.TemplateSearch' failed.
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/qubesadmin/tools/qvm_template.py", line 1527, in main
list_templates(p_args, app, 'list')
File "/usr/lib/python3.8/site-packages/qubesadmin/tools/qvm_template.py", line 1177, in list_templates
query_res = qrexec_repoquery(args, app)
File "/usr/lib/python3.8/site-packages/qubesadmin/tools/qvm_template.py", line 490, in qrexec_repoquery
raise ConnectionError("qrexec call 'qubes.TemplateSearch' failed.")
ConnectionError: qrexec call 'qubes.TemplateSearch' failed
Iâm getting this too. Iâm on the unstable branch of 4.1.
I only started looking for it once it started happening to me. SorryâŚ
My guess is thereâs a mismatch in the Python libraries or qrexec (although I could be horribly wrong)âŚ
If youâre looking to remove old versions of templates (for example, replacing Whonix 15 that came installed with Qubes 4.1 beta with Whonix 16, like I just did last week), youâve got several options, depending on how well you know what youâre doing:
Remove template and replace with downloaded RPM - A little hacky, but less chance for things to go wrong
Info on removing templates that were installed when you first installed Qubes OS: How to Remove VMs Manually | Qubes OS
You can go to ftp.qubes-os.org in a Qube and downloading the .rpm (based on your version and desired branch), and then passing it into dom0 by typing this command into a dom0 terminal (Qubes Menu > Terminals Emulator [second item in the menu]):
Wait for an update toqvm-template-repo-queryto be pushed that fixes this - Easiest option, but youâre potentially a âsitting duckâ if you use templates that are past EOL
Obviously, donât put anything in dom0 that you donât trust.
Dom0 programs can see into VMs, take things from them, add things to them, run commands, and essentially have a âgreen lightâ on your entire machine (and anything itâs connected too as well).