Same problem here, it works over Bluetooth no problem but wired it's constantly disconnecting and when i enter any game it just doesn't work at all and the light's stay off also, soon as i quit the game it turns right on again.

At first i thought it was just defective but then it worked wired/wireless with PCSX2 and i played for quite some hours so controller's fine i guess. Not sure if it's the SDL2 stuff that has been implemented / needs to be. . .

https://gist.github.com/NikoBellicRU/5935b61d616c0d1a55fcbb3b4bf7c6c0

Since you're running Proton, it sounds like the issue is related to this post? https://github.com/ValveSoftware/steam-for-linux/issues/7473#issuecomment-734518898

I am, however, having a similar problem on the Linux-native game Retro City Rampage. The DualSense works fine over Proton, but because the game has glaring sound issues over Proton, I insist on play native. The game refuses to recognize controller inputs past the first screen, regardless of Steam Input Per-Game Setting. I'm uncertain if this is something on the game's end or if this should be working at this point.

Since you're running Proton, it sounds like the issue is related to this post? [#7473 (comment)](https://github.com/ValveSoftware/steam-for-linux/issues/7473#issuecomment-734518898)

I am, however, having a similar problem on the Linux-native game Retro City Rampage. The DualSense works fine over Proton, but because the game has glaring sound issues over Proton, I insist on play native. The game refuses to recognize controller inputs past the first screen, regardless of Steam Input Per-Game Setting. I'm uncertain if this is something on the game's end or if this should be working at this point.

I also tried left 4 dead 2 wich is native with the steam for linux container it did work for a bit but then just turned off like the ones on proton, i been playing them with bluetooth and been working fine, the problem is just wired and i noticed that it also keeps disconnecting / turning off when i'm watching videos on youtube in bpm and when i exit it turns on again.

This is working perfectly now in the December 3rd beta. Thank you guys so muuuuuuuuch!!!

Ok so now it even turns off in big picture and it's also freezing steam some times when i plug the usb, i uploaded a video sorry kinda dark :/

https://www.youtube.com/watch?v=QQEzUTcfJuQ&feature=youtu.be

Also everything is in the beta

What do your systems logs look like as the controller is reconnecting?
I assume you're running with the updated udev rules?

What do your systems logs look like as the controller is reconnecting?
I assume you're running with the updated udev rules?

I'm not really into that, what logs?
When i open steam with terminal after disconecting just says this " Controller device closed after hid_read failure "

Exit steam
Open a terminal and run sudo journalctl -f
Plug your controller in
Open steam

I'm trying on pop os now and i get the same as manjaro, with that command i get that

Also sometimes i get this " usb 1-4: device descriptor read/all, error -71 "

Ok so today just to be sure i went to get a replacement controller cause it still had warranty and the problem persisted but i found out that aparently my psu was like at the limit and couldn't even keep the controller on for long. . .
I noticed this cause it would turn off on a high loads, anyway new psu and the problem is solved and even the mic is working now.

Thank's for the help :+1:

Just received the Steam (build Dec 7 2020, API v020, package version 1607372145) update on Arch and ironically, with the "Support for PS5 Controller", it actually has stopped all native Linux games from getting controller input from my DualSense, both via BT and USB.

For example, Dead Cells was working fine prior to the update with the DualSense controller in "Generic Gamepad" mode and now, ever since Steam sees the controller as a PS5 Controller, with "Playstation Configuration Support" enabled or not, no input makes it to the game. Same with Vector and Jupiter Hell.

That said, games that use Proton, such as Hades or The Witcher 3, work properly...

ETA: Yes, new udev rules are present in /lib/udev/rules.d, no reboot didn't fix it.

More ETA: sdl2-jstest detects the controller and button/axis mapping is good. DS4 controller also works properly.

Hello, @kisak-valve - can we reopen this? I'm having trouble with my Dualsense when it is connected via cable. As per original bug report, Big Picture mode works with cable and via bluetooth, but games (tested a few Proton based, so far) do not work when using a cable. Sadly, the Dualsense refuses to connect via Bluetooth when it is charging. wine control does indeed show several controllers and while there's three more or less duplicate Dualsense-like named, they all seem to generate data in the joystick-test-tab, yet not in the games - they don't even detect it.

I can check and try to debug a few things, if that would help.

Thanks, i checked that and opened #8147