| Summary: | KDE PowerDevil Shuts Off Monitor During Games | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | 382awaed |
| Component: | Power management & brightness | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | cwo.kde, kdedev, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Bazzite | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
382awaed
2025-11-07 18:30:43 UTC
Are you using a game controller? If so, this problem is already reported (and has been for a rather long time). It's unfortunately complicated to solve, as game pads do not use the regular input mechanisms that Plasma is using. A whole new approach to this is planned, but will likely still be a while off. Please let me know if this matches the issue you're having. You can start applications with the kde-inhibit wrapper, and it will turn off power management while that application is running. Steam and several other game wrappers should also handle this automatically for you. (In reply to cwo from comment #1) > Are you using a game controller? I am not using a game controller. But I am using a wooting keyboard, which is marketed as having an "analog controller" interface. I will try to see if I have their analog sdk installed, and if so remove it. thanks for letting me know about the kde-inhibit wrapper! (In reply to 382awaed from comment #2) > I am not using a game controller. But I am using a wooting keyboard, which > is marketed as having an "analog controller" interface. I will try to see if > I have their analog sdk installed, and if so remove it. Hm, is it recognized as a regular keyboard? Are there maybe some keys that work as a gamepad, and some that work as a keyboard? If it uses the regular keyboard stack, Plasma should be aware that there was an input and not turn off monitors or suspend. I'm not familiar with this brand/kind of keyboard. (In reply to cwo from comment #4) > Hm, is it recognized as a regular keyboard? Are there maybe some keys that work as a gamepad, and some that work as a keyboard? Physically, it is a standard 60% keyboard. It uses software (https://github.com/WootingKb/wooting-analog-sdk) to translate some keys into an analog "gamepad" functionality. I checked and I do not have this installed, nor is the "analog gamepad" mode within the firmware of the keyboard turned on. It seems my system simply detects it as a "generic 104-key pc" input, and i do not see any game controllers connected via the System Settings. Bazzite does include some udev rules to recognize both the normal and gamepad modes. I don't know enough about udev or kde to know if that is enough to cause this bug. This is the rule: # Wooting 60HE (ARM) SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1310", MODE="0660", TAG+="uaccess" SUBSYSTEM=="usb", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1310", MODE="0660", TAG+="uaccess" # Wooting 60HE (ARM) Alt-gamepad mode SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1311", MODE="0660", TAG+="uaccess" SUBSYSTEM=="usb", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1311", MODE="0660", TAG+="uaccess" # Wooting 60HE (ARM) 2nd Alt-gamepad mode SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1312", MODE="0660", TAG+="uaccess" SUBSYSTEM=="usb", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1312", MODE="0660", TAG+="uaccess" # Wooting 60HE (ARM) update mode SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="131f", MODE="0660", TAG+="uaccess" As an aside, given that Valve is committing to KDE Plasma for their new machines and that they are releasing a new game controller themselves, I hope they send some resources your way to fix the longstanding controller issue :) As Christoph was alluding to, it sounds very much like this fascinating piece of hardware is triggering Bug 328987. *** This bug has been marked as a duplicate of bug 328987 *** |