1
Failed to fetch template list:
Traceback (most recent call last):
File “/usr/lib/python3.13/site-packages/qubesadmin/app.py”, line
861, in qubesd_call
client_socket.connect(qubesadmin.config.QUBESD_SOCKET)
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
FileNotFoundError: [Errno 2] No such file or directory
During handling of the above exception, another exception
occurred:
Traceback (most recent call last):
File “/usr/bin/qvm-template”, line 5, in
sys.exit(main())
BmneAA
File "/usr/lib/python3.13/site-packages/qubesadmin/tools/
qvm_template.py", line 1765, in main
p_args.updatevm = app.updatevm
AAAAAAAAAAAA
File “/usr/lib/python3.13/site-packages/qubesadmin/base.py”, line
251, in__getattr__
property_str = self.qubesd_call(
self._method_dest,
self._method_prefix + ‘Get’,
item,
None)
File “/usr/lib/python3.13/site-packages/qubesadmin/app.py”, line
863, in qubesd_call
raise qubesadmin.exc. QubesDaemonCommunicationError(
“Failed to connect to qubesd service: %s", str(e)
)
qubesadmin.exc.QubesDaemonCommunicationError: Failed to
connect to qubesd service: [Errno 2] No such file or directory
2
Should non-superusers be able to capture packets?
3
Dumpcap can be installed in a way that allows members of the “wireshark” system group to capture packets. This is recommended over the alternative of running Wireshark/Tshark directly as root, because less of the code will run with elevated privileges.
For more detailed information please see /usr/share/doc/wireshark-common/README.Debian.gz once the package is installed.
Enabling this feature may be a security risk, so it is disabled by default. If in doubt, it is suggested to leave it disabled.
4
If you quit this configuration dialog, then the package being configured will probably fail to install, and you may have to fix it manually. This may be especially difficult if you are in the middle of a large upgrade.
You may need to quit anyway if you are stuck in a configuration loop due to a buggy package.
5
Should non-superusers be able to capture packets?
6
If you quit this configuration dialog, then the package being configured will probably fail to install, and you may have to fix it manually. This may be especially difficult if you are in the middle of a large upgrade.
You may need to quit anyway if you are stuck in a configuration loop due to a buggy package.
7
This tool can be used to manage templates on your system.
Installed templates are the ones currently present in the system - you can update or remove them here. Caution: updating a
template is different from updating its contents- in most cases you want to normally run the Qubes Update tool to update the
packages withing your templates. However, if a template is for some reason malfunctioning, you can try to upgrade it here,
replacing the existing template with a newer release, or reinstall it - but remember that both of those operations replace your
template with a fresh copy and all of your changes will be lost.
Available templates are the templates available online - from official Qubes OS repositories and, if enabled, from community
repositories. After installing a new template, you can switch your qubes to use it quickly using the Template Switcher tool.
This tool only displays templates installed from repositories, not any cloned or manually-installed templates.