Bug 410981

Summary: Kickoff does not search if opened with cursor under it
Product: [Plasma] plasmashell Reporter: Tasos Sahanidis <tasos>
Component: Application Launcher (Kickoff) widgetAssignee: David Edmundson <kde>
Status: RESOLVED FIXED    
Severity: normal CC: nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.16.4   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Video demonstration of issue

Description Tasos Sahanidis 2019-08-16 13:24:04 UTC
Created attachment 122175 [details]
Video demonstration of issue

SUMMARY

When launching Kickoff using the super key and with the cursor positioned under one of the tabs, any attempts to search result in Kickoff switching to the tab the cursor was on, instead of performing the search.

Moving the cursor while hovering over the tab results in the hover event being propagated and the search working again.

STEPS TO REPRODUCE
1. Move cursor to where one of the tabs would be if Kickoff was open
2. Press super to open Kickoff
3. Start typing without moving the mouse/cursor

OBSERVED RESULT

Kickoff switches to the tab the cursor was on, instead of searching.
When removing the text from the search field, the contents of the Favourite tab show, but the wrong tab is highlighted at the bottom.

EXPECTED RESULT

Kickoff should perform a search.
When the search is canceled (by removing text in the field), the correct tab should show up (the one highlighted at the bottom).

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3
Kernel Version: 5.2.0
OS Type: 64-bit
Processors: 4 × Intel® Core™2 Quad CPU Q6600 @ 2.40GHz
Memory: 7,8 GiB of RAM

ADDITIONAL INFORMATION

None
Comment 1 Nate Graham 2019-08-16 14:57:16 UTC
Fixed in Plasma 5.17 already!
Comment 2 Tasos Sahanidis 2019-12-26 11:29:13 UTC
(In reply to Nate Graham from comment #1)
> Fixed in Plasma 5.17 already!

I was unable to verify if it was fixed or not, as I had to leave this computer before KDE Neon was updated to 5.17, however I can still reproduce this bug now on a fully updated system, with the exact steps as before.

Operating System: KDE neon 5.17
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2
Kernel Version: 5.0.9-050009-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™2 Quad CPU Q6600 @ 2.40GHz
Memory: 7,8 GiB of RAM