When i am trying to attach a usb to an appvm it throws this error.
Do you have the same error when you try to attach this USB device to some other app qube?
Do you have the same error when you try to attach a different USB device to the same app qube?
I havent tested on standalone qubes or block device only usb device full on multiple appvms and tried different usbs.
Maybe your modification in the template broke something.
Install a clean template, set sys-usb template to this clean template and try to attach the USB device to the app qube based on this clean template.
I did not make any changes on my template although i will be trying that, but weirly enough this glitch happened when i exited a running dd process.
So it worked before you run this dd command?
What command was it and where did you run it?
Just a normal zero out the usb and after it returned this error. I want to say i did cntrl c and ended without finishing the process so maybe it is corrupted? But iF it can corrupt a template deep within because of this command and stop it should be considered a vulnerability. Note that sys-usb is a dvm and as such at a normal reboot should return to normal but i reinstalled templates with no success.
Here is the command:
sudo dd if=/dev/zero of=/dev/sda
Did you try to reboot the system?
Of course i did! The first thing they teatch you at school these days.
Run this command in both sys-usb and in the destination app qube:
sudo journalctl -f -n0
Then try to attach the USB device from sys-usb to the destination app qube and post the resulting logs.
I think that my pc is bricked becuase it does not display any relevant info. I will do a fresh install.
This i a bigger problem than i thought it is now being displayed at my laptop. Maybe it was a broken update? In my laptop it wont connect at all and trows no errors.
Another user having the same problem