Created attachment 108498 [details] demonstration of bug Steps to reproduce: 1. This bug requires one to have at least two activities, let's call them Activity 1 and Activity 2. 2. Unpin all applications in both activities. 3. Start a couple of applications in Activity 1. Now start another application, say Kwrite, in the same activity. Notice that it was placed at the end of task manager after all the other applications. Close Kwrite. 4. Go to Activity 2. Pin Kwrite only to Activity 2. 5. Go to Activity 1. Start Kwrite again. Expected behaviour: Kwrite should appear at the end of task manager just like it did when it wasn't pinned on another activity. What happens: Kwrite appears at the top of task manager, before other opened applications. Meaning that whether or not it is pinned in Activity 2 has an effect on where it gets placed in the task manager in Activity 1.
Perhaps all pinned apps regardless of pinned activity are rising to the top in Icons-only task manager? - there is no rising in plain Task Manager
There is also another issue (or maybe the same issue). If I pin apps A,B,C to activity 1 and then apps A,B,D to activity 2 and then move order in activity 2 to A,D,B also order in activity 1. However I couldn't find any pattern to how it changes. Seem random, for example C,A,B. I would keep order of pinned application separate in each activity. This would make it straight forward.
Same issue on 5.20 (openSUSE Tumbleweed), icons do not want to be repositioned and when they finally agree to be moved they go back up when a second one is moved. I have the same issue as elman@seznam, if different launchers are pinned on different activities they change their order randomly. All this is on latte dock, but I'm told since it uses the same libraries it is prone to the same issues.
*** Bug 464673 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2666
Git commit a67e3674bae276bf76a11df7e0d11c6195e591b8 by Fushan Wen. Committed on 27/02/2023 at 23:42. Pushed by fusionfuture into branch 'master'. libtaskmanager: consider current activity when computing first task index For example, there are two activities. Two launchers are in one activity, and 3 launchers arein the other activity. Before this change the first task index will be 5 because the index doesn't consider the current activity. After this change the first task index will either be 2 or 3 depending on the current activity. M +12 -0 libtaskmanager/launchertasksmodel.cpp M +1 -0 libtaskmanager/launchertasksmodel.h M +8 -1 libtaskmanager/tasksmodel.cpp https://invent.kde.org/plasma/plasma-workspace/commit/a67e3674bae276bf76a11df7e0d11c6195e591b8
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2678
Git commit 47b66c7147bdc559e5ecdbfa16c56b7771272b83 by Fushan Wen. Committed on 28/02/2023 at 00:12. Pushed by fusionfuture into branch 'Plasma/5.27'. libtaskmanager: consider current activity when computing first task index For example, there are two activities. Two launchers are in one activity, and 3 launchers arein the other activity. Before this change the first task index will be 5 because the index doesn't consider the current activity. After this change the first task index will either be 2 or 3 depending on the current activity. (cherry picked from commit a67e3674bae276bf76a11df7e0d11c6195e591b8) M +12 -0 libtaskmanager/launchertasksmodel.cpp M +1 -0 libtaskmanager/launchertasksmodel.h M +8 -1 libtaskmanager/tasksmodel.cpp https://invent.kde.org/plasma/plasma-workspace/commit/47b66c7147bdc559e5ecdbfa16c56b7771272b83