Bug 465651

Summary: Noticeable delay for activating hover state on task manager
Product: [Plasma] plasmashell Reporter: guimarcalsilva
Component: Task Manager and Icons-Only Task Manager widgetsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Delay while hovering

Description guimarcalsilva 2023-02-13 06:34:55 UTC
Created attachment 156184 [details]
Delay while hovering

SUMMARY
On Neon Unstable with updates as of Feb. 11th, there's a noticeable delay in activating the hover state for programs on the task manager. This happens on both X11 and Wayland and happens on Icon-only mode and task manager mode. Highlights on other widgets are normal. Also, there's no jump in CPU usage or any message on the terminal that could explain what is happening. This is not present in Plasma 5.26.5 (tested on another, slower computer).

STEPS TO REPRODUCE
1. Move the mouse cursor over various icons (check the attached video)

OBSERVED RESULT
Up to one second of delay to transition from the normal to the highlighted state.

EXPECTED RESULT
Highlights should apply instantly

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 5.15.0-60-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz
Memory: 15,6 GiB of RAM
Graphics Processor: AMD Radeon RX 570 Series
Comment 1 guimarcalsilva 2023-02-13 06:41:12 UTC
PS: I filled another bug report a few minutes ago about another similar (but not quite the same) bug with a graphics tablet, here I'm using a standard mouse, not the tablet, so this is not caused by it. I made sure to disconnect my tablet and restart the computer before recording the video.
Comment 2 Nate Graham 2023-02-13 16:39:34 UTC

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