Created attachment 172784 [details] Example of bug *** 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 When ordering icons in the task manager widget, the wrong icon is selected and reordered. This appears to affect the second and further applications which are selected and reordered, until the application focus changes. Changing focus appears to reset this condition. Until the application focus changes, whenever you try to reorder applications in the Task Manager, only the first application selected can be reordered. STEPS TO REPRODUCE 1. Drag an icon to reorder it in the Task Manager 2. Without changing focus, attempt to drag another icon to reorder it 3. Repeat. 4. Note that changing focus to another application or widget and back will reset and allow the correct application to be reordered. OBSERVED RESULT Reordering multiple applications in the Task Manager is confusing and does not work as expected. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
I can confirm the bug also exist on Arch linux ( Plasma 6.1.4 , Frameworks 6.5.0 , Qt6.7.2 , Wayland )
This is finally fully fixed in Plasma 6.2.0
I can still observe this bug with Kde plasma 6.2. I will prepare and upload a video to demostrate and give steps by steps to reproduce
Steps to Reproduce : 1- Grab/(Start to drag) one icon ( for example Kate ) 2- Move around icons ( * It will work without problem) 3- Move it over Launher menu 4- (Optional but important ) wait until lancher will pop up 5- Continue to drag 6- Observe that you are not moving the icon which you started to drag ( Not you are dragging second item on panel , in our example SystemSettings' icon ) Screen record of bug : https://vimeo.com/1017780118
Confirmed on git master with the latest instructions.
At this point, ultimately what you're seeing is Bug 491100 which is unfortunately a problem in Qt. There's an open patch, thankfully. *** This bug has been marked as a duplicate of bug 491100 ***