Bug 430084 - Changing to Alternative Task Manager Widget Unpins all Apps User has Pinned to Task Manager
Summary: Changing to Alternative Task Manager Widget Unpins all Apps User has Pinned t...
Status: RESOLVED DUPLICATE of bug 355588
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager (show other bugs)
Version: 5.20.4
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-06 16:12 UTC by Anthony
Modified: 2020-12-07 17:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anthony 2020-12-06 16:12:34 UTC
SUMMARY
When you change to a different task manager widget (e.g., from Task Manager to Icons-only Task Manager, or visa-versa), any apps not pinned by default to the task manager are unpinned.

STEPS TO REPRODUCE
1. Start an app not already pinned to the task manager;
2. Right-click on the app in the task manager and Pin to Task Manager;
3. Right-click on panel so that top-most menu entry reads "Configure Task Manager," and select "Show Alternatives";
4. Switch from Task Manager to Icons-only Task Manager, or visa-versa.

OBSERVED RESULT
Any app not pinned by default is unpinned from the task manager. 

EXPECTED RESULT
Apps pinned to task manager remain persistently pinned.

SOFTWARE/OS VERSIONS
Produced it on two versions thus far:
Linux/KDE Plasma: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
and 
Linux/KDE Plasma: KDE Neon 5.20
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
n/a
Comment 1 twinshadows404 2020-12-07 14:47:59 UTC
Can confirm.
Operating System: openSUSE Tumbleweed 20201205
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.2
Kernel Version: 5.9.11-1-default
OS Type: 64-bit
Comment 2 Nate Graham 2020-12-07 17:28:04 UTC

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