mice and keyboards stop working if enabled as HID controllers

That is a very curious backtrace...

What version of Qt are you using?

I have the same behaviour. Intermittently but more often than not, both mouse and keyboard are grabbed by Mixxx and freeze on startup. I have to disconnect and reconnect my KVM to get back control of the desktop.

This is on Debian Bullseye with both 2.2.4 and 2.3.0.

Are these HID devices and enabled in the controllers panel? I noticed that my keyboard is shown as a controller and if I enable it, it stops working while Mixxx is running.

Thank you for your response.

Q:[Be: What version of Qt are you using?]
A:Qt 5.12.8 .

Q:[Jan Holthuis (holthuis-jan) Are these HID devices and enabled in the controllers panel? I noticed that my keyboard is shown as a controller and if I enable it, it stops working while Mixxx is running.]
A:I am using Linux Mint which have not many menus to setup keyboard or mouse. Would you please guide me which command or which "system setting" menu should I look at to set the "HID devices enable/disable".

Jan was referring the Controllers section of the Mixxx preferences, not any system settings.

That's the catch!!

I disabled all controllers displayed in preferences-->Controllers. Then mouse and touch pad not freeze after start MIXXX ..

-BUT-

Those settings not lasting long. I disabled them once --> press Apply --> OK, and after restart MIXXX, those settings set to enabled again. And mouse pointer freeze after MIXXX start at the second time.

Anyway, this is the "setting" which interferes mouse behavior, for sure.

I work around by, set "Load Mapping" to "Not preset" press --> OK and exit MIXXX. Those settings are not back to Enabled (dimmed to gray color). And I do not get the freeze mouse after start MIXXX anymore.

Is this still a BUG?

Thank you all for your help.

I opened a pull request to hide mice and keyboards from the list of HID controllers so no one else gets confused by this:
https://github.com/mixxxdj/mixxx/pull/4243

> I disabled them once --> press Apply --> OK, and after restart MIXXX, those settings set to enabled again.

Do we have a clue why this happens? This seems to be the root cause of this bug that should be fixed. I remember a project where user uses a second mouse for scratching. Not sure If that's still the case.

> I disabled them once --> press Apply --> OK, and after restart MIXXX, those settings set to enabled again.

This is another bug. It is an issue of the preferences GUI getting into a confusing state. The controller is not actually enabled after disabling it and restarting Mixxx, but the Enabled checkbox is checked in the preferences, so it is easy to accidentally re-enable it. I have opened a separate bug for this: https://bugs.launchpad.net/mixxx/+bug/1941042

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/10498