Controller detection problems in Steam and Proton on Linux happen when the Proton compatibility layer fails to pass gamepad input from your controller to the game. This usually occurs after a Proton update, a Steam Input configuration change, or when gamescope interferes with input passthrough. The good news is that most of these issues are fixable with a handful of well-documented solutions.
Our team has tracked controller detection threads across the Linux gaming community for 2026, and the same fixes come up again and again. Whether you are using a DualSense, an Xbox controller, or a Switch Pro Controller, the root causes tend to overlap. The most common culprits are conflicts between Steam Input and SDL gamepad mapping, Proton version regressions, and gamescope breaking input passthrough.
In this guide, we walk through every fix in order of how often it solves the problem. We start with the quick one-liners that work for most people, then move into advanced troubleshooting like udev rules and Proton-GE installation. By the end, you will have a complete toolkit for getting your gamepad working again.
If you just want the short version: set PROTON_PREFER_SDL=1 as a launch option, make sure Steam Input is enabled with the right override, and confirm the Steam overlay is turned on. Those three steps fix the majority of reports we have seen across Reddit, GitHub, and the Arch forums.
Table of Contents
Why Controllers Stop Working in Steam Proton?
Controller detection breaks in Proton for a few predictable reasons. Understanding which one applies to your situation saves you from trying fixes blindly.
The first cause is a conflict between Steam Input and SDL. Steam tries to translate controller input through its own API, while Proton simultaneously attempts SDL gamepad mapping. When both layers fight over the same device, the game receives garbled or duplicate input, or nothing at all. This is why you sometimes see your controller detected twice or buttons mapped incorrectly.
The second cause is a Proton version regression. Valve ships Proton updates regularly, and occasionally a new version breaks controller support for specific games or controller types. The GitHub issue tracker has documented multiple regressions, including a notable one around Proton 9.0 and another that has persisted since Proton 10. In these cases, rolling back to an older Proton version is the immediate fix.
The third cause is gamescope interference. Gamescope is a Wayland micro-compositor that many Linux gamers use for borderless windowed mode or display scaling. However, it can intercept controller input before it reaches the game, effectively blocking detection. Disabling gamescope resolves this for affected users.
The fourth cause is missing udev rules. Linux requires explicit device permissions for controllers, and if your distribution lacks the proper udev rules for hidraw access, Steam may not have permission to read your gamepad. This is less common on gaming-focused distros but frequently catches new users on minimal installs.
Quick Fixes for Controller Detection Problems in Steam and Proton on Linux
These are the solutions that work most often. Try them in order before moving on to the more advanced sections.
Fix 1: Set PROTON_PREFER_SDL=1 as a Launch Option
This is the single most reported fix across every forum thread we reviewed. Setting PROTON_PREFER_SDL=1 tells Proton to use SDL gamepad mapping instead of its default input path, which resolves conflicts with Steam Input.
Right-click the game in your Steam library and select Properties. In the General tab, find the Launch Options field. Type PROTON_PREFER_SDL=1 and close the window. Launch the game and test your controller.
Multiple Reddit users in the linux_gaming community confirmed this fixed their issue immediately after Proton updates broke controller support. One user reported it solved a problem where controllers worked in Lutris but not in Steam Proton.
Fix 2: Enable Steam Input Override
Steam Input is Valve’s controller configuration system. For Proton games, you often need to explicitly enable it on a per-game basis.
Right-click the game and select Properties, then go to the Controller tab. Under the Override for dropdown, select Enable Steam Input. If it was already enabled, try switching to Disable Steam Input first, launch the game once, then switch back to Enable. This forces Steam to re-register the controller configuration.
The Arch Linux forum thread on this exact problem was solved with this approach. The user had controllers not recognized in Proton games, and enabling the Steam Input override under game properties fixed it immediately.
Fix 3: Verify the Steam Overlay Is Enabled
This surprises many people, but Steam Input relies on the Steam overlay to function. If you disabled the overlay to gain performance, you also broke controller input translation for many games.
Go to Steam Settings, then In Game, and make sure Enable the Steam Overlay while in-game is checked. This is a prerequisite for Steam Input to inject controller data into Proton games.
Fix 4: Delete and Re-register the Controller Config
If your controller is being detected twice or buttons are mapped incorrectly, you may have a stale or corrupted configuration in Steam. Open Big Picture mode, go to Settings, then Controller Settings. Find your controller, click its current configuration, and select Clear or Reset to default.
Community members report that deleting old controller configurations and letting Steam re-detect the device from scratch resolves duplicate detection and incorrect button mapping.
Understanding Steam Input vs SDL and XInput
To troubleshoot effectively, you need to understand the three input layers at play. They are the source of most controller confusion on Linux.
Steam Input is Valve’s controller API that sits between your physical gamepad and the game. It handles remapping, dead zones, trigger sensitivity, and rumble. Steam Input can translate any controller into a format the game understands, including XInput.
SDL (Simple DirectMedia Layer) is the library that most Linux-native games and Proton use for gamepad detection. SDL2 has its own gamepad mapping database that identifies controllers by their device ID and applies a standard button layout. When PROTON_PREFER_SDL=1 is set, Proton relies on this SDL mapping rather than its internal input path.
XInput is Microsoft’s controller API used by most Windows games. Xbox controllers use XInput natively, while non-Xbox controllers like the DualSense and Switch Pro Controller need emulation. Proton handles this by presenting non-Xbox controllers as virtual XInput devices to the game.
The conflict arises when Steam Input and SDL both try to handle the same controller simultaneously. The game receives conflicting input data or the controller appears as multiple devices. This is why the solutions often involve choosing one layer over the other: either let Steam Input handle everything (enable the override) or let SDL handle it (set PROTON_PREFER_SDL=1).
For most users, the combination of enabled Steam Input with PROTON_PREFER_SDL=1 as a fallback covers nearly all scenarios. Experiment with disabling one or the other if you still have issues.
Proton Version Switching and Proton-GE
When a Proton update breaks controller support, rolling back to a known-good version is the fastest path back to playing. Valve maintains multiple Proton versions simultaneously, so you can switch between them per game.
How to Switch Proton Versions
Right-click the game in Steam and select Properties, then go to the Compatibility tab. Check Force the use of a specific Steam Play compatibility tool. A dropdown appears listing every Proton version installed on your system. Select an older version and launch the game.
Based on community reports, Proton 9.0-4 has been a stable choice for controller support after regressions appeared in newer builds. Some users have also found that rolling back to Proton 8.0 resolves persistent issues with specific games.
If you do not see older versions in the dropdown, you may need to install them first. Go to Steam Settings, then Compatibility, and check the box to Enable Steam Play for all other titles. This exposes additional Proton versions for installation.
Installing Proton-GE for Better Controller Support
Proton-GE (GE-Proton) is a community-maintained fork of Proton that includes additional patches, updated dependencies, and fixes that have not yet made it into official Proton releases. Many Linux gamers consider it the best option for controller compatibility.
The community consensus from Reddit threads is clear: controllers that fail with standard Proton often work immediately with Proton-GE. One user reported that controllers simply do not work unless they use Proton-GE, an issue that has existed since Proton 10.
To install Proton-GE, download the latest release from the GE-Proton GitHub repository. Extract the archive into your ~/.steam/root/compatibilitytools.d/ directory. If that directory does not exist, create it. Restart Steam, and the new GE-Proton version will appear in the compatibility dropdown.
Alternatively, use a tool like ProtonUp-Qt, which automates the download and installation process. It provides a graphical interface for managing multiple Proton-GE versions and is available as a Flatpak.
Checking ProtonDB for Game-Specific Controller Advice
ProtonDB is the community database where Linux gamers report compatibility for individual games. Before spending hours troubleshooting, search for your game on ProtonDB and filter reports by controller-related keywords. Other users may have already found the exact Proton version and Steam Input setting that works for that specific title.
Gamescope and Controller Conflicts
Gamescope is popular for its ability to run games in a nested compositor, enabling features like integer scaling, HDR, and custom resolutions. However, it can break controller detection by intercepting input events before they reach the Proton session.
If you launch games through gamescope and your controller is not detected, the first thing to test is launching without it. Remove gamescope from your launch options and try running the game directly through Proton. If the controller works without gamescope, you have found the culprit.
The GitHub issue tracker for Proton documents this exact scenario. Multiple users reported that disabling gamescope restored controller functionality after a Proton update broke it. The gamescope workaround is one of the more reliable fixes in the community.
If you need gamescope for other reasons, check whether a newer version has resolved the issue. Gamescope is under active development, and input handling improves with each release. You can also try passing specific gamescope flags related to input handling, though results vary by game.
udev Rules for Controller Permissions
This is the fix that almost no guide covers, but it solves problems for users on minimal or custom Linux installations. Linux controls device access through udev rules, and if Steam does not have permission to read your controller’s hidraw device, detection fails silently.
What Are udev Rules and Why They Matter
udev is the Linux device manager that sets permissions when hardware is connected. When you plug in a controller, udev determines which users and processes can access it. Gaming-focused distributions like SteamOS, Bazzite, and ChimeraOS ship with comprehensive udev rules that grant Steam access to gamepads. Minimal distros or server installs may lack these rules entirely.
How to Install Controller udev Rules
The Steam client installs its own udev rules during setup, but they can be missing or outdated. First, check whether the rules exist by looking for files in /usr/lib/udev/rules.d/ or /etc/udev/rules.d/ with names containing “steam” or “valve”.
If they are missing, the simplest fix is to reinstall Steam, which should place the rules files automatically. Alternatively, Valve maintains the official controller udev rules in the Steam GitHub repository. Download the rules file and place it in /etc/udev/rules.d/.
After installing or updating udev rules, reload them with the command sudo udevadm control –reload-rules && sudo udevadm trigger. Unplug and replug your controller to apply the new permissions.
Checking hidraw Permissions
To verify whether Steam can see your controller, run ls -la /dev/hidraw* while the controller is plugged in. You should see entries where the group or owner grants read and write access. If permissions look restrictive, your udev rules need updating.
You can also run lsusb to confirm the controller is recognized at the kernel level. If lsusb shows the device but Steam does not detect it, the problem is permissions or Steam Input configuration, not hardware.
Controller-Specific Fixes
Different controllers have different quirks on Linux. Here is what to watch for with the most common gamepads.
Xbox Controllers (Series X/S, One, 360)
Xbox controllers have the best out-of-box experience on Linux because most Windows games expect XInput natively. The Xbox Wireless Controller works over USB and Bluetooth without additional drivers on modern kernels. If you experience disconnections over Bluetooth, ensure your kernel is version 5.15 or later, which improved Xbox Bluetooth stability significantly.
If Steam detects your Xbox controller but the game does not, try disabling Steam Input entirely. Since the game expects XInput and the Xbox controller provides it natively, Steam Input can actually get in the way by adding an unnecessary translation layer.
DualSense and DualShock 4
Sony controllers work well on Linux through the hid-sony and hid-playstation kernel drivers. The DualSense (PS5) and DualShock 4 (PS4) are both supported, but games that expect XInput need Steam Input or SDL to translate their input.
For DualSense users, enabling Steam Input with the controller set to Xbox configuration layout is the most reliable setup for Proton games. This presents the DualSense as an XInput device to the game, which most Windows titles handle without issues.
If you want the DualSense’s adaptive triggers and haptic feedback to function, you need games that support the native DualSense API, which is rare outside of PlayStation ports. For most Proton games, XInput emulation is the practical choice.
Nintendo Switch Pro Controller
The Switch Pro Controller works over Bluetooth and USB on Linux, but it requires Steam Input for most games because its button layout differs from Xbox conventions. Enable Steam Input and select the Gamepad configuration to remap the buttons correctly.
A common issue with the Switch Pro Controller is that the buttons appear inverted (A and B, X and Y swapped) because Nintendo uses a different button naming convention. Steam Input handles this automatically when you use the Gamepad configuration, but if you disable Steam Input, the mismatch will confuse the game.
Generic and Third-Party Controllers
Generic gamepads may not be in the SDL gamepad mapping database, which means SDL cannot identify them. If your controller is not recognized even with PROTON_PREFER_SDL=1, you can create a custom SDL mapping string using the SDL_GAMECONTROLLERCONFIG environment variable. Tools like SDL2’s gamepad tool or the antimicrox utility help you generate the mapping string for your specific device.
Frequently Asked Questions
Why is Steam not detecting my controller on Linux?
Steam may not detect your controller because of a conflict between Steam Input and SDL gamepad mapping, a Proton version regression, missing udev rules for hidraw device permissions, or gamescope intercepting input. The fastest fix is to set PROTON_PREFER_SDL=1 as a launch option, enable the Steam Input override in the game’s controller properties, and confirm the Steam overlay is enabled.
How to fix Steam not recognizing controller?
To fix Steam not recognizing your controller, first set PROTON_PREFER_SDL=1 in the game’s launch options. Then right-click the game, go to Properties, select the Controller tab, and set the override to Enable Steam Input. Make sure the Steam overlay is enabled in Steam Settings under In Game. If those fail, switch to Proton-GE or roll back to an older Proton version like 9.0-4.
How to stop Steam from detecting controllers?
To stop Steam from detecting controllers, go to Steam Settings, then Controller, and disable controller support. You can also set the controller override to Disable Steam Input on a per-game basis by right-clicking the game, selecting Properties, going to the Controller tab, and choosing Disable Steam Input from the Override for dropdown.
How do I enable Proton Linux compatibility with Steam games?
To enable Proton for Steam games on Linux, go to Steam Settings, then Compatibility, and check Enable Steam Play for all other titles. Select your preferred Proton version from the dropdown. For specific games, right-click the title, select Properties, go to the Compatibility tab, check Force the use of a specific Steam Play compatibility tool, and choose a Proton version from the list.
Wrapping Up
Fixing controller detection problems in Steam and Proton on Linux comes down to understanding how Steam Input, SDL, and XInput interact. The most effective fixes, in order, are setting PROTON_PREFER_SDL=1 as a launch option, enabling the Steam Input override per game, confirming the Steam overlay is on, and switching to Proton-GE or rolling back your Proton version if a regression is to blame.
For persistent issues, check your udev rules for hidraw permissions, disable gamescope if you are using it, and consult ProtonDB for game-specific advice. These solutions cover the vast majority of controller detection failures reported across the Linux gaming community in 2026. Start with the quick fixes, then work through the advanced steps until your gamepad is back in action.