You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you checked for updates in Settings > System?: Yes
Please describe your issue in as much detail as possible:
I'm using a Steam Deck for fighting game tournaments, especially our local weeklies. It works really well, except for one annoying thing that has been present from the very start: every time a Playstation controller is connected via USB, the system switches both output and input to it automatically. I think it's very valuable that it's possible to do this, but I don't think it's good default behavior.
I thought an easy fix might be to add these controllers to the blocklist for the switch-on-connect module, but that module doesn't even seem to be loaded by PipeWire, so I'm not sure what to do about it now. I thought I should go ahead and file this issue since apparently nobody else has.
Steps for reproducing this issue:
Dock a Deck to an external monitor with audio output
Have audio output
Plug in a DualShock 4 or DualSense controller
Lose audio output
Go to audio and see that the default outputs and inputs were switched to the controller
The text was updated successfully, but these errors were encountered:
Your system information
Please describe your issue in as much detail as possible:
I'm using a Steam Deck for fighting game tournaments, especially our local weeklies. It works really well, except for one annoying thing that has been present from the very start: every time a Playstation controller is connected via USB, the system switches both output and input to it automatically. I think it's very valuable that it's possible to do this, but I don't think it's good default behavior.
I thought an easy fix might be to add these controllers to the blocklist for the switch-on-connect module, but that module doesn't even seem to be loaded by PipeWire, so I'm not sure what to do about it now. I thought I should go ahead and file this issue since apparently nobody else has.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: