If I connect a wireless (even though encrypted) mouse to dom0 I guess security dives? That is what I gathered so far.
I have a sys-usb, it was created “by the installation process”, i.e. I have not created it manually. The logi dongle is registered there in the drop down from the tray, together with other units like the camera par example(I think, can’t remember exactly at the moment). If I attach the logi dongle to a machine the mouse works. Except lack of cursor.
I am connecting the mouse to the untrusted AppVM in order to not expose dom0 or other more critic VMs to wirelessness and USB so to speak (security reasons) . I don’t mind the keyboard being connected (it works, also logi over same dongle) to a VM where I read the news, surf for best doughnuts in Portland or play point-and-click adventures. With the machine handling for example banking I only use the laptop keyboard and touch pad and that is fine, not many minutes a month. But generic surfing and Monkey Island would benefit from a mouse. (and I am always curious how to get things to work, that’s how I learned most I know about Linux : )
IF the problem is solved by connecting it to dom0 it is done. But if security is compromised that would be suboptimal. Now, I might have missunderstood the “do not attach to dom0, bad for security” and then I have cost my self - and you - lots of time
I have been thinking about a clean Qubes install. Rationale being that things happened when I fiddled with Solaar, instead of having to manually deny the keyboard 7 times I now have to deny the mouse, but only one time. This together with the installation being wobbly (see first post) and the screen flickering quite a lot intermittently maybe it would be worth a try. I have the feeling this could all be hard ware related (some components was replaced a couple of months back when a USB C port stopped working with USB 3.0 units, not 2.0!) Then again, when I had Windows installed everything was hunky dory. What do you think?