Bug 444398 - Application Launcher (KickOff) not working with Wacom tablets
Summary: Application Launcher (KickOff) not working with Wacom tablets
Status: RESOLVED DUPLICATE of bug 445111
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) widget (show other bugs)
Version: 5.23.1
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-25 23:54 UTC by Santiago Shang
Modified: 2021-11-10 14:22 UTC (History)
6 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Santiago Shang 2021-10-25 23:54:21 UTC 
SUMMARY
I can't click inside the icons to open an application in favorite or navigate in the side bar categories menu.

STEPS TO REPRODUCE
1. Using a Wacom tablet, Click on Plasma Kickoff Menu
2. Click in any Application Icon or section inside the menu(i.e. Favorites)
3. Any icon doesn't respond to the action.

OBSERVED RESULT
The kickoff menu is useless with a wacom tablet at this time. In the Past version it worked perfectly.


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-10-26 13:24:07 UTC 
Can confirm. Hover with a stylus works, click does not.
Comment 2 Santiago Shang 2021-10-26 14:58:25 UTC 
(In reply to Nate Graham from comment #1)
> Can confirm. Hover with a stylus works, click does not.

So strange... Because hover doesn't work for me the most of time. check this:
https://twitter.com/kdecommunity/status/1452764870718459907
Comment 3 Nate Graham 2021-10-26 15:15:19 UTC 
Urgh, it uses a MouseArea to handle click and drag, which has no conception of styluses. :/ We would need to port to TapHandler + HoverHandler, and re-work how drag-and-drop is accomplished--again! :(
Comment 4 huyizheng 2021-11-10 12:08:38 UTC 
It seems that plasma 5.23.3 fixes this issue.
Comment 5 Nate Graham 2021-11-10 14:22:59 UTC 
Aha, must have been the same as Bug 445111, which was fixed recently and the fix released in Plasma 5.23.3.

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