Bug 480555

Summary: Wrong mouse cursor when rearranging non-open application on icons-only task manager
Product: [Plasma] plasmashell Reporter: John Dykes <98johndykes>
Component: Task Manager and Icons-Only Task Manager widgetsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: nate, niccolo.venerandi, notmart, qydwhotmail
Priority: NOR Keywords: qt6, regression
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Wrong icon on icons only task manager

Description John Dykes 2024-01-30 17:13:16 UTC
Created attachment 165359 [details]
Wrong icon on icons only task manager

SUMMARY
When rearranging pinned applications on the icons-only task manager, if the application is not open, then we see an "X" icon instead of a hand icon, even though we can rearrange the icons.


STEPS TO REPRODUCE
1. Pin some applications to the icons only task manager.
2. Rearrange an application that is not open.

OBSERVED RESULT
The icon shown is a red X

EXPECTED RESULT
The icon is a hand, as is the case when rearranging an open icon.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 39
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.0
Kernel Version: 6.6.13-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6750 XT

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-01-30 21:32:53 UTC
Can reproduce. Looks like it's fallout from https://invent.kde.org/plasma/plasma-desktop/-/commit/f6e6e3d85afb588ebf597f0651bd64a7dabc8ff7. We should only see this icon when dragging over another part of the panel outside of the Task Manager, not the Task Manager itself.
Comment 2 Nate Graham 2024-02-13 04:31:51 UTC
Actually it looks like that commit is not the direct cause as I can reproduce the issue even after reverting it.
Comment 3 Nate Graham 2024-02-21 20:02:56 UTC
The issue appears to be fixed now as of current git master, as I can't reproduce it anymore, but I could earlier.