Application Launcher stops responding after showing logout screen

Help
,
1

After pressing Ctrl+Alt+Del or pressing the power button on my computer case (these trigger the logout screen), the Application Launcher stops responding to Meta key press. sudo showkey shows that Meta key is being pressed ‘keycode 125 press, keycode 125 release’; however, nothing happens unless I press Alt+F1, or right click the desktop or panel (which allows me to press Meta key to open App Launcher again). I also tried installing ksuperkey, which worked, but I couldn’t figure out how to make it run on startup via systemd (“Unable to connect to X11 display. Is $DISPLAY set?” then exit-code). I know it’s not really that big of a deal, but it still bothers me. Is there any solution to fix this issue? I’m very new to this, so I’m not really well-educated on debugging issues myself.

Display Server: X11
KDE Plasma 6.3.5

2

Hi! To help folks best guide you, could you please provide your basic system information from the Info Center app? The Copy Details button is the easiest way to get that ready to paste in:

info-center
info-center1399×578 85.3 KB

And just checking, does the issue also occur in a Wayland session?

3

I checked in Wayland, and it seems like the problem doesn’t occur there.

Operating System: Arch Linux
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.1
Kernel Version: 6.15.1-arch1-2 (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i7-11700 @ 2.50GHz
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 5700 XT
Manufacturer: ASUS

4

Thanks - I wonder if that’s an edge case that wasn’t covered by the fix to this bug, perhaps? 503938 – Keyboard shortcuts for KDE Application Launcher don't work (X11)

5

I made another shortcut for the Application Launcher (Ins key), triggered the logout screen with Ctrl+Alt+Del, and I was still able to open the App Launcher with Ins key.

6

I will just find a way to make a start-up script with ksuperkey. The issue still persists. I don’t think there’s a fix for this, and I seem to be one of the few people that has reported this issue so it’s probably not worth figuring out anyways.