Why doesn't my new Logitech MX Master 3S mouse work on Qubes? (It works fine on PopOS (Ubuntu based))

I do not want to use Bluetooth. I want to use their USB bolt receiver that came with the mouse.

When I plug this USB bolt receiver into Qubes (4.2), it is recognized by the USB qube. However, the MX Master 3S mouse does not work. (By the way, this same receiver works fine with my new Logitech MX Keys S keyboard - both devices are paired to the same receiver.)

However when plugging this receiver into the USB on a different machine with PopOS (Ubuntu based), the mouse works fine. (And so does the keyboard.)

What could be the issue?

BTW, in case it matters: I used a different macOS machine to pair both devices to the receiver using a downloaded Logitech program (because I don’t want to install proprietary Logitech software on my Linux machines).

Meaning, I didn’t install any special Logitech program on the PopOS. Everything “just worked” there. I’m hoping to achieve the same on my Qubes.

It’s not as simple on QubesOS.

Read this:

1 Like

Ok, but…

My previous (older) MX Master 3 (not 3S as my latest) was working fine before this with its receiver. It’s a different USB receiver (don’t ask me why Logitech keep changing the receivers too) but the point is, it “just worked” on Qubes.

Could this be because this (the older MX Master 3) was the mouse I used when clean installing Qubes 4.2 and somehow during the installation more “magic” automatically takes place to make sure the mouse is setup?

Some devices are not working properly using usb passthrough: android devices, xbox controllers

Your mouse may use something new compared to the previous one, making it incompatible with the current USB widget. I advise you to report the bug, hopefully it could be fixed :slight_smile:

1 Like

Do you have another USB mouse to test if it’ll work or not?

I am using this mouse - also with the USB bolt receiver.
I am not sure if I remember it correctly but I think I always had to accept that I want to use this device when I started Qube - until I whitelisted it. Now I start Qubes & it just works.

I am not sure how we can debug this - but you can be sure that it works (somehow :wink: )
(PS: I also use the mx keys s with the usb bolt received - it also works fine!)

1 Like

Could this have something to do with this error I get, when I insert the USB bolt receiver into my USB port? “Denied qubes.InputTablet from sys-usb to dom0”.

Do you get this error too? This error seemed irrelevant, since I have no tablets, so I didn’t mention it before. (Could this mouse technically be a “tablet” for some reason?)

So far, I have simply been ignoring this error (and cancelling the file transfer dialog that pops up too). Like I mentioned earlier, the keyboard still works fine. For some reason, the mouse doesn’t.

What do you mean by this? Didn’t get this part.

Maybe your mouse is detected as a tablet instead of a mouse.
You need to allow the qrexec request for your mouse to work.
The input devices qrexec policy is set in Qubes Global Config → USB tab and you can change it so that your USB tablet (mouse) will be allowed by default without asking you every time.

1 Like

Thanks, giving this permission made the mouse work.

Previously I didn’t give this permission because this transfer dialog to dom0 scared the hell out of me, for some reason.

1 Like