58
The weirdest issue I've fixed so far
(lemmy.today)
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
That includes posts generated by LLMs. It doesn’t matter if you “don’t have the time” or “would’ve written the same anyway”, or if “everyone’s doing it geez get with the times”.
For now it’ll also include “AI”-assisted projects that haven't had at least two months of (public, verifiable) dev time behind them.
Help:
Launchers/Game Library Managers:
General:
Discord:
IRC:
Matrix:
Telegram:
Thanks but I can figure it out myself. (Prolly am gonna forget about this tho until it becomes an issue again).
Feel free to hit me up when it does bother you again. I didnt fix mine until I had to.
Could you post your solution here when you get the time? Don't have the issue, but would love to know how udev was used to solve the issue for if I ever encounter the problem myself.
Sure but it is per device, I am basically telling my system "this is not a joypad". Its just a rule in udev. You'd need to get these values from your own device. Each vendor and product will have one.
Thank you for the example. I have the same keyboard brand too so definitely nice to have. I think I can use lsusb to find my values.