Well, yeah. On the surface, that seems perfectly reasonable. But what is a user to do when both teams are either pointing the finger at the other or shrugging their shoulders? Not to mention one of the first times I used this key was on a VBox version of Whonix (inside Mac or Debian… can’t remember) and it worked just fine. That is another reason for me to suspect that it is related to Qubes.
I don’t have the understanding that many here do of the Qubes implementation of Whonix, but that’s my point - how else am I supposed to know about possible factors if I don’t ask? And when the lead developer of Whonix says “Qubes-Whonix has no special code that changes anything related to keyboard. Please contact Qubes support.” what would you do?
I am posting here because it seems that there could be unknown factors on the Qubes end that might be causing this problem. The most obvious is the manner in which dom0/qrexec manages the attachment of the device to whonix via sys-usb. From my admittedly uneducated perspective, that seems like the most obvious source of the trouble. I have no idea. I’m not even sure how to troubleshoot such a thing.
And, of course, there could be some issue with the device itself. What if the device developers cut some corner when writing the firmware? Both Qubes and Whonix might be doing everything right but it doesn’t work. But again, I have no idea if that’s the case if I don’t start eliminating other possible causes. I’m still waiting to hear back from the developers of the key.
Above all, I sincerely appreciate your patience and understanding as I sort this out.