Proton 10 not seeing controller nor mouse inputs
Hi, don't know why but couple games when on proton 10 doesn't pass through controller inputs, same goes for mouse. As for mouse it only recognises left click, but I can't click in menus.
Doesn't matter if I use controller as wireless or if plugged in.
Tried so far:
- proton 10.0-1 beta
- proton experimental
- proton tkg 10.6
- proton GE 10-1
Version which work:
- Proton GE 9-27
I tested proton 10 on freshly installed standalone Fedora Kinoite 42 on my second disk and I don't have these problems.
Sample game which has this problem:
- Mafia Definitive Edition
Not gonna lie it's kinda annoying since I see that I have better performance on 10s comparing to 9.
59 Replies
I just had a problem about gamescope not letting me click on a dialog with GE-Proton-10-1, let me downgrade and see
bazzite base:
Haven't updated yet to newest one but still might be problem with it.
Maybe I'm missing something comparing to plain Kinoite or there's something which causes it? I asked couple people with other distros and they don't have this problem, be it said Kinoite or Arch.
Already tried removing layered apps and still the same.
I'm having the same issue. I have a Flydigi Vader 3 Pro and it doesn't work on any games using Proton 10. I tried with both Proton Experimental and GE 10-3
I've done all updates, its still the problem. Switched to raw kinoite and no problems. This is something on bazzite, even ruled out plasma problems as gnome has the same problem on bazzite.
I'm also on the latest updates and the issue still persists, it's really annoying having to select Proton 9 for games instead of using the latest Proton 10
same goes for mouseSorry to say but I am completely unable to reproduce this I have used nothing but Proton-10 and ProtonGE 10-1 for the last few weeks Not one game has issues w/ mouse input I will test controllers later today
Mouse also works fine for me
I have re-tested controller on Proton Experimental and GE 10, and on the latest Bazzite update I still have the issue, neither of my controllers work
Did you find any fix?
Proton 9 does not have this issue
In proton 10 even in ge controller just stops working after suspend resume
@arkejn did anything work out for you in the end with proton 10
@Rondo Revolution did anything work out for you in the end?
Having the same issue
Nope, but Kyle Gospo is aware of the issue, so it's probably a bit of time before it's fixed
For now I'm using Proton 9 and GE 9
Didn't he say he couldn't reproduce it? :/
just the mouse part, which is also not affecting me, but is affecting the other user
Is this a bazzite only issue or does it affect steamos too
I don't know for sure, but from what I have seen it's probably a bazzite only issue
Tested this today, I am completely unable to reproduce any issues with input
Controllers work perfectly fine on both proton 10 and proton GE 10-3
I tested this on my desktop which uses a desktop image, and my htpc which uses a deck image
I also tested it for the actual controls of my handheld which also runs a deck image
There is no difference with how input works on bazite versus Fedora or any other distro for controllers
And no reason to believe this would be specific to us
If you want further debugging on this you are going to have to reproduce this in a way that produces actionable logs, but I will ask another maintainer to test as well just to be sure
If it helps, I'm using the desktop image, is there any logs I can provide to help?
Also, there is an open issue on Proton GitHub of another Bazzite user with the same issue: https://github.com/ValveSoftware/Proton/issues/8681
GitHub
Controllers don't work in game anymore · Issue #8681 · ValveSoftw...
Your system information Steam client version (build number or date): 1745876290 Distribution (e.g. Ubuntu): Bazzite Opted into Steam client beta?: No Have you checked for system updates?: Yes Steam...
I commented there a few days ago
I also tested with another controller and still have the same issue. I tried with a Flydigi Vader 3 Pro, a custom Pi Pico controller and a Dualsense, none of them works on Proton 10, but works fine on earlier versions
Out of curiosity: are you using PROTON_ENABLE_WAYLAND=1? I had that happen when I tried that.
Tried it on one game once only, all the other tries were without the launch option for wayland
Okay, so that's not it then.
Just tested with Proton 9 and 10 on Heroic Games Launcher to be sure the issue was not on Steam, and same results :/
nope, still same thing. standard desktop mode since it's PC, I don't like big picture/gaming mode. Switched to GE 9-27.
It's strange for me that I installed kinoite for testing and ootb it just works on 10.x, while bazzite, even with newest build just doesn't work.
recognizing click for action like shooting works with mouse but everything else is just inoperable.
Haven't tested it in a while besides after last update tho. I will try this week probably as been busy.
Same thing actually with ZZZ via lutris. Wanted to try wine-10.6-staging-tkg-ntsync how it fares on 6.14 kernel and no controller detection 😶 checked any other 10.x build and ye only going back to any proton GE 9.x and it instant recognizes controller. Will have to check on Kinoite
Just downloaded Stellar Blade demo, same thing, 10.0-1 and It doesn't see my controller at all, swapped to GE 9-27 and it instantly recognized it in main menu
Tested in five more games, still can't reproduce
also everything I tested is without using steam input
I tested on Katana Zero, Blasphemous 2, Cuphead and Street Fighter 6, none of them has controller working with Proton 10, Experimental or GE 10
It works normally on any Proton 9 version
I tried with both Steam Input on and off
I also tried in Big Picture, but doesn't work either
Forgot to mention, but also tried with games on Heroic Games Launcher, with the same result
Is my current image, but like said before I already tried to remove non-oem packages and issue persists.
I can gladly try to troubleshoot it more.
And with it on?
just checked, nope
Yeah sorry, no clue
I can't reproduce this with any controller on any hardware with any game
Whatever is going on you all are going to have to tell me once you have absolute certainty. If I can't reproduce it I can't debug it.
You're out of date
20250603 is the latest
yeah I see, was checking on Sunday last update, downloading
My system was also outdated, I updated it, and also did a
rpm-ostree reset to be sure, but same result so farye same but of course denuvo on stellar blade hit activation limit :Deadge:
Anyway what I notice as well is that when on 9-27 it renders game's cursor, while on 10.x I have only system cursor rendered.
ok so I've tested and installed fresh bazzite on secondary ssd.
didn't add anything, tried as is after update to latest 20250603.
It's the same problem, mouse is only recognized that it left clicks into the void, but no option to click precisely what I want.
Controller also doesn't work.
So I have no idea what is different with Kinoite that makes it work.
Steam just added support for the additional Flydigi Vader controllers in D-Input mode and I thought it would help, but unfortunately it still doesn't work on Proton 10, only on Proton 9 and earlier versions.
I have a laptop with Bazzite that I'll test it on when I can to see if it also happens there
This issue is still not fixed I've seen multiple other threads with the same issue. This footage here has the game played in ge proton 10-4 and as you can see I just did a simple sleep restart and the game input is totally gone until I restart it again
Same game everything's the same all I did was change to ge proton 9-27 and it works normally
My ally's running the latest bazzite just updated it yesterday and it's still like this
The issue occurs if I -
a) Sleep then resume
b) Switch power state aka pull out the charger or put the charger in
If any of these two happens controller input is instantly gone for the game but not for steam ui that works perfectly fine
I just rebased to stock kinoite and suddenly every problem disappears. It's definitely something with bazzite cause I won't believe it's my system. So good luck for rest of you :Okay:
ok I tinkered a bit, for some reason openrgb does that and probably udev rules causes it. @Rondo Revolution do you have rgb on your rig and use openrgb?
I haven't used OpenRGB in a while, but I definetely used it on this bazzite install in the past, do you know which udev rule file might be the culprit?
there should be
60-openrgb.rules
either in etc/udev/rules.d/ or /lib/udev/rules.d/I do have the file in
/lib/udev/rules.d/unfortunately I do not know if this rule is preinstalled or is it installed with openrgb. before I had openrgb layered but now I installed flatpak and had to add rule manually. After reloading rules and restarting it started to act up. Once removed, reloading and restarting problem with mouse and controller is gone
after
sudo udevadm control --reload-rules && sudo udevadm trigger it didn't work so had to restart but I'm confident this is my culprit.installing openRGB doesn't install any rules
those rules are pre-installed in every bazzite install
Every test the dev team has done where they were unable to reproduce this issue were completed with those rules in place
almost certainly not the issue
yeah, unfortunately I don't think that's related to the issue I'm having
I tried taking out the few udev rules I had set up and tried using an empty openrgb rule in case /etc/udev/rules.d takes is the last one being loaded, but neither worked
also tried adding a udev rule specifically for my controller, but same thing on proton 10 :/
did you restart your system after reloading rules? cause I can add manually rules, reload them and controller suddenly stops for me, but to revert it I had to remove rules, reload, then restart system
and I'm able to reproduce it atm every single time
yep, I restarted after every change
I just managed to test it on my laptop with Proton Experimental and the issue is definitely on my desktop install
I can't do a backup and reinstall right now, so that sucks, I have no clue what might be the issue
found also this https://github.com/atar-axis/xpadneo/issues/457
OpenRGB (may mess up mappings and rumble stability)We don't ship xpadneo
Ok, I have now reinstalled Bazzite and restored a backup of my home folder, but the issue persists
I'll try installing it on a spare ssd I have and testing it again, but I'm not confident the issue is on my system anymore
Ok, after further testing I believe the issue is with Bazzite
I made a fresh install on an external SSD I have, and the issue is still present there. After that I rebased to the nvidia image since that's what my laptop has where it works, the issue persisted. After that I rebased to Kinoite, enabled third-party repos and installed Steam. The issue persisted, but after deleting the steam folders in my home directory, and letting steam recreate it, my controller worked correctly on Proton 10. All tests were done with Proton Experimental
I'll test again on the nvidia image to be sure by letting steam recreate the folders
Also, I tried to let steam recreate folders in my main install right now, and the issue still persists, no input from controllers on Proton 10
But that install in on the amd image
Yeah, made no difference being the amd or the nvidia image
I don't know why, but so far the issue is only present on Bazzite for me
On Kinoite it works fine
Maybe its an issue with the Steam package present on Bazzite repos?
it's the fedora one
and if it was -- literally any bazzite developer would be able to reproduce this issue
I doubt the problem is in our image at all
I see, do you know anything I can try to narrow down what might be the issue?
It's buggin the hell out of me
Specially since it only affects Proton 10 and I can make it work on a fresh Kinoite install, but not a fresh Bazzite install
narrow down exactly what controllers you're testing
on what games
on what hardware
so we can run our own tests
unless we can reproduce this it's not getting fixed
Oh ok, here's all the info you asked:
Hardware:
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 5700 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450 AORUS PRO WIFI
Software:
Operating System: Bazzite 42 (Desktop image)
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-106.bazzite.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Games tested:
Katana Zero, Risk of Rain 2, Cuphead, Blasphemous II, Balatro, Street Fighter 6, Sekiro
Controllers used:
Dualsense;
Flydigi Vader 3 Pro both in DInput (needs latest Steam Beta) and XInput;
Custom leverless controller (Raspberry Pi Pico/RP2040 with GP2040-CE firmware in XInput mode)
Proton versions:
Tried all controllers in Proton Experimental and Proton 9, none works on Experimental or any other version of Proton 10.
If there's any other info I need to provide or logs that I need to send, I'll gladly do
Sorry to bother, but has there been any update on this? Unfortunately I still can't use Proton 10 with controllers
Also little update: I found a workaround, if I use Proton GE with the recent added option
PROTON_PREFER_SDL=1 %command% to the game it seems to work, I'll further test it, but for now it worked on FF7 Remake
Update: while the workaround I mentioned before does work, since it disables Steam Input, I can't remap the extra buttons on my controller. I just tested it on my spare drive install and I can only have controllers working on Proton 10 on Kinoite. :dispair:Have similar issues on my end with both a DS5 (bluetooth and wired) and an 8BitDo Ultimate controller via its dongle. Any version of Proton 10 (GE, Experimental, or official Beta) across all games. Desktop Image with NVIDIA drivers.
I mainly notice it if I alt+tab out of the game or otherwise make the game lose focus i.e. I brought up the Steam overlay in game once and that also killed controls. Steam Input on or off. OS itself still recognizes inputs from controllers, though.
Does not occur on CachyOS, Fedora 42, regular Arch, or Debian Stable. Likewise on SteamOS on my Steamdeck. Also doesn't occur on Proton 9 or lower.
I did notice the same SDL solution above did work, as did forcing wayland in GE10-10 (since that also forces SDL) with no issues. Could alt+tab without controls being lost. Unfortunately not a complete solution as some games don't play nice without Steam Input, but hey.
For info on my system
Hardware:
Processor: AMD 9800X3D
Memory: 16GB RAM
GPU: NVIDIA 3080 10GB Founders Edition
MOBO: ASRock B850M Pro RS Wifi
Software:
Operating System: Bazzite 42 KDE Desktop Image with NVIDIA drivers. Validated updates on it.
Games tested:
Ys 1&2 Chronicles+, Ys VI: Ark of Napishtim, Clair Obscure: Expedition 33, Rise of the Ronin, Grim Fandango HD, Sam & Max Save The World. Steam Input on and off in all (where I could actually still get controls without Steam Input, that is)
Controllers used:
Dualsense via Bluetooth & Wired;
8BitDo Ultimate 2.4g Controller with dongle in XInput mode.
Proton versions:
Proton 10 Beta
Proton Experimental
GE Proton 10-4 through 10-10
GE Proton 9-27
Proton 9
I also have similar issue in game mode with Proton 10 (I use GE-Proton), while controller input works normally, it seems that mouse input are strictly focused on the first launched proton-layered app, meaning that if I switch to another app using Steam Overlay, any mouse action (clicking mostly) will be executed on the first launched proton-layered app/games
Did a quick test with the new Proton 10.0-2 (beta) Valve put out in Ys Origin with my DS5, and same issue. I alt+tab once and lose controller input entirely while OS and Steam itself still seem to be taking inputs. Didn't do much additional testing but I don't suspect any other results to be much different.
Setting back to GE 9-27 results in controls returning just fine.
Similar issue, works on 10-GE with
PROTON_PREFER_SDL=1 %command% or switching to 9 works also.
Weird thing is that on the new Ninja Gaiden it work without any special settings for a couple of times an then when i paired a new controller (don't know if it had anything to do with it) it stopped working.