Bug 500493

Summary:	KRunner doesn’t respond to shortcuts
Product:	[Plasma] krunner	Reporter:	Andrija <andrija.urosevic27>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	alexander.lohnau, cwo.kde, natalie_clarius
Priority:	NOR
Version First Reported In:	6.3.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

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.