SUMMARY The bluetooth remote control works only after firing a 2nd signal / button press, because whatever the first is, it is used for lighting up the screen and not for the action any user would expect. STEPS TO REPRODUCE 1. Put Strawberry player to play music. 2. Leave the computer withuot any keyboard / mouse / bluetooth controller input, so the screen saver launches. 3. Wait longer until the screen turns off. 4. Press the "next", "play/pause", "stop" or some bluetooth remote control you know that usually triggers some action in your system. 5. The first button / signal does nothing but to "wake up" or activate the screen. 6. Now you can trigger some other action by pressing any button of the remote control of the bluetooth device, and it works as expected. OBSERVED RESULT The user needs to press first some button in order the screen "awakes", before triggering some action through a 2nd button press. EXPECTED RESULT The action from the bluetooth device, that goes to the music player controller, should go directly, without the need of activating the screen before. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: ArchLinux (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Graphics Platform: Wayland Graphics: AMD Radeon Vega 10 Graphics
Sounds like the same root cause as Bug 488516, where it was discovered that input isn't getting accepted until the screen wakes up. *** This bug has been marked as a duplicate of bug 488516 ***
Fully fixed as of 4-Jul-24 (actually some weeks ago, but I can't remember the exact date). Operating System: Arch Linux KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.6.36-1-lts (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 13,6 GiB of RAM Graphics Processor: AMD Radeon Vega 10 Graphics Manufacturer: Acer Product Name: Aspire A315-42 System Version: V1.11