view the rest of the comments
Unpopular Opinion
Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
- If your post is a "General" unpopular opinion, start the subject with [GENERAL].
- If it is a Lemmy-specific unpopular opinion, start it with [LEMMY].
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry. Please also refrain from gatekeeping others' opinions.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
People in this thread have noted that some systems seem to be Linux-cursed, and I've definitely experienced that. Usually it's a specific piece of hardware that isn't well supported, or a package or default configuration that has an issue. I've had systems that were spinning their heads and spraying pea soup everywhere on OpenSUSE and Debian turn around and behave perfectly on Gentoo (that was 17 years ago, but it doesn't seem to be a unique experience).
Regarding the controller, if you're connecting a PS4 controller via bluetooth I think I had the same problem earlier today, and there's an issue open on the bluez github about it. I found a post on the Arch bbs with a workaround. TLDR, bluez has had a few issues in the latest builds and reverting all your bluez libraries to 5.68-1 seems to solve it for most people, including me. Unfortunately, this kind of thing crops up occasionally. Everywhere really, but especially on Linux because of how much it relies on community contributions to projects.
Anyway, I've rambled too long. Sounds like you got bit by either a driver issue or a config/package issue. Sorry it happened to you, and sorry it soured you on Linux. If you're looking for something that "just works" and aren't getting it with Linux, no reason to beat your head against a wall.
oh its two different controllers, both connected via usb, a switch pro controller (recognized as a 360 controller) and an 8bitdo pro 2 controller