Bug 490059

Summary:	Icons-and-Text Task Manager reordering issue: Trying to drag a second icon, will drag the previous one instead
Product:	[Plasma] plasmashell	Reporter:	saunders
Component:	Task Manager and Icons-Only Task Manager	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	asturm, benjamindaines, bugseforuns, chermnykh2001, Christoph.Wolk, dannkunt, m.kurz, pallaswept, paul, postix, qydwhotmail
Priority:	NOR
Version:	6.1.2
Target Milestone:	1.0
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	settings 1 settings 2

Description saunders 2024-07-10 22:38:46 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Reordering tasks put the task manager into a state where it stop working properly.
My settings are in the uploaded pngs.

STEPS TO REPRODUCE
1. Click on a task, drag it to a different position.
2. Click on another task and drag it to a different position as well.
3. Tasks will jump around and be randomly ordered.
X. The "fix" is click and drag, then click on the task you just dragged one time then everything will behave.

OBSERVED RESULT
Tasks start randomly moving to the wrong position.

EXPECTED RESULT
Move to and stay in the correct position.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
Operating System: Gentoo Linux 2.15
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.8 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 3950X 16-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4070/PCIe/SSE2

ADDITIONAL INFORMATION

Comment 1 saunders 2024-07-10 22:39:07 UTC

Created attachment 171552 [details]
settings 1

Comment 2 saunders 2024-07-10 22:39:19 UTC

Created attachment 171553 [details]
settings 2

Comment 3 cwo 2024-07-10 23:19:32 UTC

Does your version of qt have the patch from https://bugs.kde.org/show_bug.cgi?id=489107? I don't think the official qt release does, as 6.7.2 was released on June 19, and the patch was merged into the 6.7 branch on June 21.

Comment 4 Andreas Sturmlechner 2024-07-11 17:17:57 UTC

(In reply to cwo from comment #3)
> Does your version of qt have the patch from
> https://bugs.kde.org/show_bug.cgi?id=489107? I don't think the official qt
> release does, as 6.7.2 was released on June 19, and the patch was merged
> into the 6.7 branch on June 21.
There's no patch in there.

Comment 5 cwo 2024-07-11 17:25:19 UTC

I apologize, I copied the wrong link. Should be https://bugs.kde.org/show_bug.cgi?id=482770

And this is the patchset in question: https://codereview.qt-project.org/c/qt/qtwayland/+/565408

Comment 6 saunders 2024-07-11 18:38:52 UTC

In the screenshots "Sort" should be set to "Manual", not "Do Not Sort". I set it to the wrong thing for the screenshot. I use "By Desktop" for the time being until it's fixed. Apologies.

Comment 7 saunders 2024-07-11 19:37:15 UTC

Just recompiled dev-qt/qtwayland-6.7.2-r1 with the patch mentioned and no change unfortunately.

Comment 8 postix 2024-07-13 12:42:57 UTC

Can confirm on openSUSE TW and Plasma 6.1.2. 

What happens (for me) is that when have dragged a task A and try to drag task B afterwards, it will drag task A instead again.

Comment 9 filip.kendes1 2024-09-03 18:00:16 UTC

*** Bug 492610 has been marked as a duplicate of this bug. ***

Comment 10 pallaswept 2024-09-08 04:50:54 UTC

Just saw this bug mentioned on a reddit post. This bug seems like it's a dupe of this one https://bugs.kde.org/show_bug.cgi?id=491100

I'm running the patch from that issue and it does work.

Comment 11 m.kurz 2024-09-12 22:23:36 UTC

Can also confirm this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=491100
I am also running the patch mentioned there (https://codereview.qt-project.org/c/qt/qtwayland/+/581714) it fixes the problem.

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