protonscr

[Controller] PS5 DualSense all of a sudden not working

steamclosed Distro Family: UbuntuGeneral controller / Steam Input
ValveSoftware/steam-for-linux#11969 · opened 2025-05-02 by rbullers · updated 2025-05-08 · 3 comments · github
Rrbullers 2025-05-02 github

Your system information

  • Steam client version (build number or date): 1745876290
  • Distribution (e.g. Ubuntu): Pop!_OS 24.04 LTS (based on Ubuntu)
  • Opted into Steam client beta?: [Yes/No] Yes
  • Have you checked for system updates?: [Yes/No] Yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: Nvidia 3070Ti (Drivers: 570.133.07)

Please describe your issue in as much detail as possible:

I have been using my PS5 Dualsense controller via Bluetooth for a few weeks without any issues, with Steam Input disabled. Today all of a sudden it has stopped working in games.

Steam itself detects the controller, and all buttons respond as expected when clicking the Begin Test button. I can also use Big Picture Mode with the controller.

I attempted the following:

  1. Restarting my machine
  2. Removing Steam completely and purging all related Steam data
  3. Tested with Steam Input on and a custom template for a specific game
  4. Removing the controller from Bluetooth and re-pairing

I didn't notice any issues when looking at the controller.txt logs myself, but hope someone can spot something.

Image

Steps for reproducing this issue:

  1. Unsure how to reproduce.
Rrbullers 2025-05-03 github

This issue can be closed, I believe the problem was with Proton, as switching to Proton-GE resolved the issue.

Aalasky17 2025-05-05 github

@rbullers Since this is a Proton bug - it would be great if you could file an issue here instead :) https://github.com/ValveSoftware/Proton/issues. And please mention which games you are seeing this problem on if you file an issue there (and please also tag me). 🙏

Aalasky17 2025-05-08 github

@rbullers We just shipped an experimental build which hopefully contains a fix for the controller disconnection issue. Could you please let me know (and file an issue in the Proton tracker) if you are still seeing this issue on Proton - Experimental?

Nothing extracted yet.