https://bugs.kde.org/show_bug.cgi?id=517818
Bug ID: 517818
Summary: Controller stops responding when launching proton game
with steam input disabled, only if kde has started
Classification: Plasma
Product: kwin
Version First 6.6.2
Reported In:
Platform: Bazzite
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: libinput
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
I am trying to play Clair Obscur in proton with a DualSense PS5 controller via
bluetooth. This was previously working with steam input disabled on
bazzite-deck-gnome.
After switching to bazzite-deck with kde, I now find that if I disable steam
input, the controller works at the point in time the computer has booted
directly into the game mode (gamescope session w/ steam deck ui).
However if I switch from gamescope to kde, upon launching the game, the
controller stops responding, and is no longer visible in steam or kde's
controller kcm. It isn't be usable again until I disconnect it from bluetooth,
powering down the controller, and turning it on again. This doesn't occur with
steam input enabled, however then the controller is treated as an Xbox
controller and displays xbox-style glyphs. Therefore it is ideal that it works
with steam input disabled. Behaviour is the same between official proton 10.0
and proton-em with wayland backend.
Summary:
Steps to reproduce:
- Launch Clair Obscur with steam input disabled while running kde/kwin/plasma
Observed result:
- Controller doesnt work and dissappears from steam and system settings kcm
Expected result:
- Controller works
SOFTWARE/OS VERSIONS
Operating System: Bazzite 43
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.17.7-ba28.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Proton: 10.0-4, EM-10.0-35-HDRTEST
Controller: Dualsense Wireless over Bluetooth
--
You are receiving this mail because:
You are watching all bug changes.
