usb attach failure

[loftlifter31]

How to file a helpful issue

Qubes OS release

4.2.3

Brief summary

Trying to pass a usb device (phone) to an app qube results in a pop up error that qubesd passed an empty response and this in the journalctl log.

Nov 25 14:23:36 dom0 qrexec-policy-daemon[2365]: qrexec: qubes.USB+4-3: phone-admin -> sys-usb: allowed to sys-usb
Nov 25 14:23:41 dom0 qubesd[2361]: unhandled exception while calling src=b'dom0' meth=b'admin.vm.device.usb.Attach' dest=b'phone-admin' arg=b'sys-usb+4-3' len(untrusted_payload)=0
Nov 25 14:23:41 dom0 qubesd[2361]: Traceback (most recent call last):
Nov 25 14:23:41 dom0 qubesd[2361]: File "/usr/lib/python3.11/site-packages/qubesusbproxy/core3ext.py", line 634, in on_device_attach_usb
Nov 25 14:23:41 dom0 qubesd[2361]: await vm.run_service_for_stdio('qubes.USBAttach',
Nov 25 14:23:41 dom0 qubesd[2361]: File "/usr/lib/python3.11/site-packages/qubes/vm/qubesvm.py", line 1596, in run_service_for_stdio
Nov 25 14:23:41 dom0 qubesd[2361]: raise subprocess.CalledProcessError(p.returncode,
Nov 25 14:23:41 dom0 qubesd[2361]: subprocess.CalledProcessError: Command 'qubes.USBAttach' returned non-zero exit status 1.
Nov 25 14:23:41 dom0 qubesd[2361]: During handling of the above exception, another exception occurred:
Nov 25 14:23:41 dom0 qubesd[2361]: Traceback (most recent call last):
Nov 25 14:23:41 dom0 qubesd[2361]: File "/usr/lib/python3.11/site-packages/qubes/api/init.py", line 297, in respond
Nov 25 14:23:41 dom0 qubesd[2361]: response = await self.mgmt.execute(
Nov 25 14:23:41 dom0 qubesd[2361]:
Nov 25 14:23:41 dom0 qubesd[2361]: File "/usr/lib/python3.11/site-packages/qubes/api/admin.py", line 1306, in vm_device_attach
Nov 25 14:23:41 dom0 qubesd[2361]: await self.dest.devices[devclass].attach(assignment)
Nov 25 14:23:41 dom0 qubesd[2361]: File "/usr/lib/python3.11/site-packages/qubes/devices.py", line 251, in attach
Nov 25 14:23:41 dom0 qubesd[2361]: await self._vm.fire_event_async('device-pre-attach:' + self._bus,
Nov 25 14:23:41 dom0 qubesd[2361]: File "/usr/lib/python3.11/site-packages/qubes/events.py", line 234, in fire_event_async
Nov 25 14:23:41 dom0 qubesd[2361]: effect = task.result()
Nov 25 14:23:41 dom0 qubesd[2361]: ^^^^^^^^^^^^^
Nov 25 14:23:41 dom0 qubesd[2361]: File "/usr/lib/python3.11/site-packages/qubesusbproxy/core3ext.py", line 648, in on_device_attach_usb
Nov 25 14:23:41 dom0 qubesd[2361]: sanitized_stderr = santizied_stderr[:-2] + "."
Nov 25 14:23:41 dom0 qubesd[2361]: ^^^^^^^^^^^^^^^^

Steps to reproduce

1. connect usb device
2. attach usb device to app qube

Expected behavior

device attaches

Actual behavior

doesn't attach, generates error above

[marmarek]

duplicate of #9545

[github-actions]

This issue has been closed as a "duplicate." This means that another issue exists that is very similar to or subsumes this one. If any useful information on this issue is not already present on the other issue, please add it in a comment on the other issue. Here are some common cases of duplicate issues:

• The other issue is closed. The other issue being closed does not prevent this issue from duplicating it. We will examine the closed issue and, if appropriate, reopen it.
• The other issue is for a different Qubes release. We usually maintain only one issue for all affected Qubes releases.
• The other issue is very old. The mere age of an issue is not, by itself, a relevant factor when determining duplicates.

By default, the newer issue will be closed in favor of the older issue. However, we make exceptions when we determine that it would be significantly more useful to keep the newer issue open instead of the older one.

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

If anyone reading this believes that this issue was closed in error or that the resolution of "duplicate" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.

[loftlifter31]

This is not a duplicate. There is a bug in the error handler which was referenced in the issue you linked to, and that does show up here as well because it affects everyone on 4.2, but there is another error beyond that. See the first 15 lines of the error log I posted above.

[marmarek]

Then please try with the fixed package (it's in current-testing repo) and see what happens.