I renamed this thread ‘R4.1 user bug reports’ so I’m not spamming the board while I play around with 4.1
The most recent update to dom0 (Oct 3 DRPMs that include
binutils 2-34-5.fc32) made my USB keyboard input unstable–it no longer works most of the time, but occasionally works for no discernable reason.
- sys-usb is based on debian-10-minimal and has three packages installed:
- tasket’s vm-boot-protect and configure-sudo-prompt applied
/etc/qubes-rpc/policy/qubes.InputKeyboard has been modified to include
sys-usb dom0 allow
- Warning notifications (multiple repeats) appeared whenever sys-usb was started (along the lines of “@admin qubes.InputKeyboard failed”). After QubesOS reboot, these notifications no longer appear
- USB mouse unaffected
Possibly related but most likely not:
When unmounting a USB device from a qube, there’s a notification indicating that the detachment is in progress but there’s nothing to indicate that the detachment is complete. In 4.0.3 the end of detachment is marked by notifications showing that the device(s) are available, as if they were just plugged in.
Edit: 3 days later: The problem somehow resolved itself. There was a large-ish update across all templates and dom0, so one of those (or a combination) is likely to have done the trick. Not knowing how to further probe and troubleshoot is giving me insights into why less-scientific cultures resort to superstition to deal with the whimsical (to them) natural environments they inhabit.
l have a feeling it won’t be long before I write posts on how to find solutions to your latest Qubes 4.1 problem via chicken entrails.