Bug 489808 - Krunner hotkey becomes "sticky" until eventually failing to launch.
Summary: Krunner hotkey becomes "sticky" until eventually failing to launch.
Status: REPORTED
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 6.1.2
Platform: NixOS Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-06 03:05 UTC by stayingintheshade
Modified: 2025-03-11 20:06 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stayingintheshade 2024-07-06 03:05:22 UTC
SUMMARY
When repeatedly opening krunner via the keybind (alt + space, alt + f2, etc) it will begin failing to open, requiring multiple presses of the keybind to show up. It will eventually get to the stage where one must hold down the keybind, rapidly triggering it over and over, to get krunner to appear. Eventually, krunner will not open at all until restart. Note that this ONLY occurs when the text entered into krunner is left as is, any changes to the text field will "reset" this effect. 

STEPS TO REPRODUCE
1. Open krunner via the keybind, enter a couple characters of text.
2. Do not change the text. Begin pressing the keybind repeatedly to open and close krunner.
3. Continue until krunner's keybind becomes "sticky" and eventually fails to open altogether.

OBSERVED RESULT
Krunner will no longer respond properly to the keybind, first requiring multiple presses to appear until eventually failing to appear altogether from the keybinds.

EXPECTED RESULT
Krunner opening in response to the keybind consistently.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.6.36
Graphics Platform: Wayland

ADDITIONAL INFORMATION
At first I thought this could be related to my Nvidia GPU, so I got my friend to test it on an all AMD system, in which he was able to reproduce the bug identically. We both had the same KDE Plasma, KDE Frameworks and Qt version.
I was also able to reproduce the bug with all search plugins except for "Applications" disabled.
Comment 1 limelier 2024-10-23 07:37:03 UTC
I can also reproduce this, also on Plasma 6.1.2 on Wayland. It makes krunner practically unusable for long periods of time. A workaround is to just pkill krunner, but the issue will start happening again fairly soon.
Comment 2 Tom 2024-10-24 14:25:20 UTC
I can also reproduce this bug on Plasma 6.1.2 with Wayland.

System info:
Operating System: Arch Linux 
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B46
System Version: 1.0
Comment 3 Tom 2024-10-25 16:53:47 UTC
I saw this line in the syslog when the bug occured, I think it is relevant to the bug.

25.10.24 18:51	krunner	qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5f972ec8e650
Comment 4 Cherkah 2025-03-11 20:06:34 UTC
+1
I also find myself in the situation where after using Krunner a few times, the search field no longer appears.
I can only use Krunner again after rebooting  :/

Operating System: EndeavourOS 
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVIDIA GeForce GTX