When dragging items in the icons-only task manager with not quite slow mouse movements, various glitches can be observed: The dragged item changes, sometimes it glitches and sometimes even random items swap position (not in the video though). Also, after a restart the taskmanager does not remember some of the icons positions. I did not open a separate report for that as I believe that issue is related. Reproducible: Always
Does this happen only when dragging pinned tasks, not-pinned tasks, or both?
It does not matter what kind of task I drag.
I forgot to mention: This is a regression as it worked just fine before 5.7.0 (so before the new taskmanager backend)
This happens on all my systems updated to 5.7.x, so it's not dependant on the configuration/cache.
Just installed latest plasma (-desktop, -workspace(-libs), -frameworks) from git and the issue is the same.
> Also, after a restart the taskmanager does not remember some of the icons positions. Those would obviously only be remembered for pinned tasks, FWIW.
(In reply to Eike Hein from comment #6) > > Also, after a restart the taskmanager does not remember some of the icons positions. > > Those would obviously only be remembered for pinned tasks, FWIW. Yes, as I said in comment 2, both kinds of tasks are affected. My guess is that there is some mismatch between the visible position and the internal one.
Same here https://gfycat.com/FragrantEasygoingFlounder I even see some rearrangements if i run application after this from dockbar.
Thanks for your reports, hopefully we get to fixing this soon.
I tried to reproduce this today but haven't been able to so far.
I am able to reproduce this issue on Plasma alsmost-5.7.95, with a clean, default config. By replacing the task manager with the icons only one and opening several windows for testing (kwrite, firefox, qt dbus viewer, qtconfig, dolphin and konsole) the issue appears when dragging items around quickly.
AIUI though you were able to verify it only happens on Qt 5.6.x, right? Seems all 5.7+ users can't reproduce it. Personally I'm not able to support Qt 5.6.x any longer.
Hello! 5.7 is hard masked on gentoo. So you can confirm that it is qt 5.6 problem?
(In reply to lmk from comment #13) > Hello! 5.7 is hard masked on gentoo. So you can confirm that it is qt 5.6 > problem? Not with 100% certainty, but I haven't come across this issue on Qt 5.7 yet.
I can't reproduce it (5.7/5.8) and Kai can't either, and for Fabian it went away when switching to 5.7.
(In reply to lmk from comment #13) > Hello! 5.7 is hard masked on gentoo. So you can confirm that it is qt 5.6 > problem? It runs OK... It's only masked for minor build issues (i.e. Quality Control): https://bugs.gentoo.org/show_bug.cgi?id=589412 # Michael Palimaka <kensington@gentoo.org> (12 Aug 2016) # Requires revdeps to build with at least C++11. Bug 589412. # Masked for wider testing. But it's running as well as any Qt 5.x version on my Gentoo install (i.e. all the old bugs are still present :-) )
hello! can confirm that switching to qt 5.7 did the trick. Thank you.