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.
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.
save