Bug 500493 - KRunner doesn’t respond to shortcuts
Summary: KRunner doesn’t respond to shortcuts
Status: RESOLVED DUPLICATE of bug 480800
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 6.3.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-20 22:59 UTC by Andrija
Modified: 2025-02-21 08:16 UTC (History)
3 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 Andrija 2025-02-20 22:59:46 UTC
SUMMARY
At the boot any default and custom shortcuts for the KRunner work as intended, but the first time I call the KRunner using the shortcut and dismiss it wit escape key, it won’t be able to show the search bar again until I terminate the session(reboot or log out).

STEPS TO REPRODUCE
1. run the krunner
2. close it without typing anything inside the search bar
3. run the krunner again - it does not respond

OBSERVED RESULT


EXPECTED RESULT
KRunner should popup even after I dismiss it, like it did in the previous versions of Plasma.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700KF
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4080

ADDITIONAL INFORMATION
KRunner version is 6.11.0-1 and I am using Wayland.

When running krunner in terminal:
➜  ~ krunner
QThreadStorage: Thread 0x5e62419ab030 exited after QThreadStorage 4 destroyed
QThreadStorage: Thread 0x5e62419ab030 exited after QThreadStorage 3 destroyed
➜  ~
Comment 1 cwo 2025-02-20 23:26:38 UTC
Thank you for the bug report! This issue is already being tracked; marking as a duplicate.

Unfortunately, this is a nvidia driver issue, and there is not really anything we can do from our end at this point. You can restart krunner with "krunner --replace" but it will only work once so you'll have to do it each time (and krunner will start somewhat slowly as it has to reload everything each time.

*** This bug has been marked as a duplicate of bug 480800 ***
Comment 2 Andrija 2025-02-21 08:16:39 UTC
Got it! Thanks for letting me know.