Linux Gaming

15906 readers

41 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago

MODERATORS

poVoq@slrpnk.net

Quintus@lemmy.ml

mudle@lemmy.ml

KDE cares about your input [devices] (lemmy.ml)

submitted 1 month ago by JRepin@lemmy.ml to c/linux_gaming@lemmy.ml

20 comments fedilink hide all child comments

The KDE Goals initiative is working to improve support for input devices such as game controllers, fancy mice, handhelds — anything for your gaming needs.

This Sunday, Oct 20th at 18:00 (UTC), the KDE Goals champions will be answering your questions live. Post your questions here and I'll make sure they'll answer them.

We'll be streaming here: https://tube.kockatoo.org/w/2tAyknEQc8EhL2AyoAUE8M

You can get in touch with the community at the Matrix room.

you are viewing a single comment's thread
view the rest of the comments

[–] UnRelatedBurner@sh.itjust.works 5 points 1 month ago

What do you mean by "I'll make sure they'll answer them"? Are you a reporter? But if this is a bug report thread now, here I go:

I have and one of my friends had the Logitech G502 LIGHTSPEED mouse. It has a problem with it's mouse wheel.

I've done the debugging a while back, but maybe I can get the logs again. Basically when using it wired it only uses the regular mouse wheel events, but when using it wireless (most of the time) it uses both highres mwheel events and regular ones. Confusing all apps. To add to this, the regular events seems to be simulated by software, based alongside every 5th (? maybe it was a long time ago) highres event. While at seemingly random times a full "click" of the mouse wheel just doesn't register the required number of highres events, making the "normal" one also absent. I tough this was a hardware issue, as when it happens you can go back and forth and it won't register it at all, however it doesn't happen when pugged in.

This is probably some kernel issue if I'm being honest, all I know is that on Windows it works perfectly. But I am using KDE and I have not debugged this mouse on any other window manager.

I truly don't know if this was the type of reply you were looking for, if not: Sorry for wasting your time. (There's also a KDE bug when editing widgets or when turning the screen off and on, but that's not input device so)