Bug 507367

Summary:	When cursor at rest overlaps a just-launched krunner menu, the item under the cursor gets selected / focused
Product:	[Plasma] krunner	Reporter:	AndyKluger
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	alexander.lohnau, AndyKluger, natalie_clarius, nate
Priority:	NOR	Keywords:	X11-only
Version First Reported In:	6.4.3
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Video demo of the issue

Description AndyKluger 2025-07-22 15:11:13 UTC

SUMMARY

This is the same as resolved issue https://bugs.kde.org/show_bug.cgi?id=372635 "do not follow mousepointer when accessing krunner via keyboard" -- but for current versions of Plasma.

When I launch krunner, if the cursor happens to already be in an area that the new krunner menu uses, the menu item under the cursor gets selected. This leads to surprises and accidents if I don't take care to check for this occurrence before hitting enter.

STEPS TO REPRODUCE
1. Configure krunner to launch in the center of the screen
2. Move the cursor to the center of the screen
3. Launch krunner
4. Type something
5. Hit enter

OBSERVED RESULT

The sixth menu item action is performed.

EXPECTED RESULT

The first menu item action is performed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION

X11 session

Comment 1 AndyKluger 2025-07-22 18:27:01 UTC

Created attachment 183441 [details]
Video demo of the issue

I've added a video demo of the issue, wherein I:

- hit alt-space to launch krunner
- type "kde"
- hit enter

Comment 2 AndyKluger 2025-08-04 14:46:28 UTC

In case my explanation and video aren't clear, the problem is also described at:

- https://bugs.kde.org/show_bug.cgi?id=379910
- https://bugs.kde.org/show_bug.cgi?id=379859
- https://bugs.kde.org/show_bug.cgi?id=374044
- https://bugs.kde.org/show_bug.cgi?id=373154

Comment 3 Nate Graham 2025-09-24 19:06:43 UTC


*** This bug has been marked as a duplicate of bug 508524 ***