I am glad you were successful in solving that problem. I was reading some of the same documentation about USBs where they were providing some insight about how to manage USB attachment and thought I should create a sys-usb since I skipped that step during initial configuration.
On the other, I currently So, I tried to create a sys-usb in order to prevent rubber ducky attacks but I ended up killing my mouse.
At first, I made a VM called sys-usb with network connection using the create new-app-VM function (thinking it was that simple), then I found in the docs, the best method to make a sys-usb was to write
qubesctl state.sls qvm.sys-usb
in dom0, which I did. The log response was promising as no errors were returned.
Unfortunately, on my next restart my mouse was inactive. I tried a few different USB ports and nothing.
I returned to the docs to see, if there was a fix for this in usb-qubes.md and they suggested to default the system to accept all usb-mice.
So, I looked for the script/package qubes.Inputmouse but I did not find it. So, I deleted the new-app-VM and tried the mouse again but nothing happened.
Finally, I tried the suggested steps to create the file by writing the following:
[user@dom0 ~]$ qubesctl state.sls qvm.sys-usb
and this is what was returned :
Data failed to compile:
No matching sls found for 'qvm.sys-usb' in env 'base'
DOM0 configuration failed, not continuing
At this point,I want to get my USB Mouse working again.
I looked for the qubes.InputMouse to see if I could add the suggested code to have my mouse attached but I did not find the file in qubes-rpc.
I am hoping someone would know how to fix this.