I also tried to uninstall.
Check the created policy files
And so on.
Btw: qubes-video-companion-dom0 was updated yesterday with a new versions string:
4.3.2
Pulled and installed was 4.3.1
EDIT:
the reason was not the installation of qubes-video-companion (this triggers only the qubesd.service restart)
the root cause was removing a “devices_denied” Rule in the qubes-global-config/Device Assignment
no Changes to files in this folder since installation of system
device_protocol.py
Checked the code lines mentioned in the error message, but my python knowledge is not so good to understand at which points the variables are filled.
So what is the source of the variable Interfaces?
Is it qubesvm.py get the information via
import qube.config
All informations I found are related to /var/lib/qubes/qubes.xml
So I,v done one ‚shot in the blue‘ and recover the backup of /var/lib/qubes/qubes.xml which was done round about 1 hour before i installed qubes-video-companion.
After that i was able to restart qubesd
Puhhh well, that’s makes me happy again.
And now the interesting part:
Feb 13 11:24:55 dom0 qubesd[9181]: File "/usr/lib/python3.13/site-packages/qubes/app.py", line 1040, in __init__
Feb 13 11:24:55 dom0 qubesd[9181]: self.load(lock=lock)
Feb 13 11:24:55 dom0 qubesd[9181]: ~~~~~~~~~^^^^^^^^^^^
Feb 13 11:24:55 dom0 qubesd[9181]: File "/usr/lib/python3.13/site-packages/qubes/app.py", line 1135, in load
Feb 13 11:24:55 dom0 qubesd[9181]: vm.load_properties(load_stage=2)
Feb 13 11:24:55 dom0 qubesd[9181]: ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
Feb 13 11:24:55 dom0 qubesd[9181]: File "/usr/lib/python3.13/site-packages/qubes/__init__.py", line 757, in load_properties
Feb 13 11:24:55 dom0 qubesd[9181]: setattr(self, name, value)
Feb 13 11:24:55 dom0 qubesd[9181]: ~~~~~~~^^^^^^^^^^^^^^^^^^^
Feb 13 11:24:55 dom0 qubesd[9181]: File "/usr/lib/python3.13/site-packages/qubes/__init__.py", line 276, in __set__
Feb 13 11:24:55 dom0 qubesd[9181]: value = self._setter(instance, self, value)
Feb 13 11:24:55 dom0 qubesd[9181]: File "/usr/lib/python3.13/site-packages/qubes/vm/qubesvm.py", line 146, in _setter_denied_list
Feb 13 11:24:55 dom0 qubesd[9181]: sorted(map(repr, set(DeviceInterface.from_str_bulk(value))))
Feb 13 11:24:55 dom0 qubesd[9181]: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^
Feb 13 11:24:55 dom0 qubesd[9181]: File "/usr/lib/python3.13/site-packages/qubes/device_protocol.py", line 763, in from_str_bulk
Feb 13 11:24:55 dom0 qubesd[9181]: raise QubesValueError(
Feb 13 11:24:55 dom0 qubesd[9181]: ...<2 lines>...
Feb 13 11:24:55 dom0 qubesd[9181]: )
Feb 13 11:24:55 dom0 qubesd[9181]: qubes.exc.QubesValueError: Invalid length of interfaces='None' (is 4, expected multiple of 7)
Feb 13 11:24:55 dom0 systemd[1]: qubesd.service: Main process exited, code=exited, status=1/FAILURE
can somebody please do the same and confirm?
Steps to reproduce:
add a rule “Device Attachment Policy”
delete this rule again
check /var/lib/qubes/qubes.xml if this line exist in description of the related qvm:
<property name="devices_denied"></property>
restart qubesd at dom0; sudo systemctl restart qubesd
The qubesd should fail to start
To fix:
remove line from /var/lib/qubes/qubes.xml and restart qubesd again
Is this a bug of the GUI?
Maybe the property “devices_denied” has not to be empty?
In my opinion this is a major bug, because the user didn´t recognized the issue, during working with gui.
