You can sign up to get a daily email of our articles, see the Mailing List page!

Did you do a big system upgrade recently and notice you're having gamepad issues? You're not alone. Time to downgrade perhaps.

To be clear this might only be an issue for the more bleeding-edge distributions which update more often, or those of you who are doing some manual updates to their system. The distributions that update more slowly like Ubuntu are likely unaffected right now.

First we have systemd version 243 released around September 3rd, this appears to be causing problems with Steam Input. A Valve developer jumped into the comments there, to note that the update seems to have broken Steam's udev rules to support gamepads—ouch. The systemd developers have been responsive trying to fix it, so hopefully it won't be too long before the issue is solved there.

Another problem is the more recent release of the Linux Kernel 5.3, which appears to have a regression with the DualShock 4 over Bluetooth not working. As of yet, no Kernel developer has commented on that report.

Hat tip to Vash63.

Article taken from GamingOnLinux.com.
23 Likes, Who?
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG, Humble Store and Paradox Interactive. See more here.
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
26 comments
Page: 1/3»
  Go to:

Termy 16 Sep, 2019
I've had 5.3 rc7 and 243 for a while (manjaro reverted back to 242 in the meantime), and didn't notice any issues with my xbox 360. At least not in Project Cars 2.
djazz 16 Sep, 2019
So that's why controllers in steam stopped working last week. Loading the module 'uinput' fixes it, as that is what Steam uses to create virtual controllers.
tkonicz 16 Sep, 2019
I have severe problems with Dualshock4 and the Switch Pro-controller on Debian 10 after updating to Kernel 5.2 via Backports. It could run deeper than just Kernel 5.3 and new systemd
Faalhaas 16 Sep, 2019
This new systemd messed me up as well. I have to do a sudo modprobe uinput to get the Steam Controller working in-game.

Even after that, some games did not detect my buttons, so I even reinstalled the OS. Now it's working with modprobe.
gustavoyaraujo 16 Sep, 2019
Yes, I'm having some issues with my Nintendo Wii U Pro controller. I hope they will fix this soon.
Nibelheim 16 Sep, 2019
Yep, 1 week without controller in game but it works on Steam menu.

Thank you for the tip, I didn't found any solution before.
razing32 16 Sep, 2019
Ouch.
Have not played games with a controller recently.
Hope the modprobe is enough to fix it.
hallieballie 16 Sep, 2019
I really do not understand why systemd is so great, it is an annoying system to deal with.

When you need to debug form a rescue environment, it is very difficult to see what went wrong, to access logging is science these days.

The time with init scripts was heaven, now we are in hell.
F.Ultra 16 Sep, 2019
Quoting: hallieballieI really do not understand why systemd is so great, it is an annoying system to deal with.

When you need to debug form a rescue environment, it is very difficult to see what went wrong, to access logging is science these days.

The time with init scripts was heaven, now we are in hell.

When you need to debuf from a rescue environment with the old init scripts you would be lucky if you where able to find any form of logs at all. On a systemd system though everything can be found with journalctl, even things that daemons wrote to stderr or stdout are caught.

As a server admin, systemd is the single best thing that have happened to Linux since the kernel.
Hori 16 Sep, 2019
Quoting: hallieballieI really do not understand why systemd is so great, it is an annoying system to deal with.

When you need to debug form a rescue environment, it is very difficult to see what went wrong, to access logging is science these days.

The time with init scripts was heaven, now we are in hell.
In my experience systemd offered quite a lot of features when creating a service unit file, giving you a lot of control over how it behaves, its timings and boundaries, etc. I find it really easy to use and yet very powerful.
For the regular user I don't know, but I create a lot of programs that I run in the background as services, and for me it's great.


Last edited by Hori on 16 September 2019 at 7:04 pm UTC
While you're here, please consider supporting GamingOnLinux on:

Patreon, Liberapay or PayPal Donation.

We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register

Or login with...
Sign in with Steam Sign in with Twitter Sign in with Google
Social logins require cookies to stay logged in.

Livestreams & Videos
Community Livestreams
Latest Forum Posts