Bug 471949 - (Classic) Task Manager - Unpinned applications keep re-showing after reboot
Summary: (Classic) Task Manager - Unpinned applications keep re-showing after reboot
Status: RESOLVED DUPLICATE of bug 470604
Alias: None
Product: kded-appmenu
Classification: Plasma
Component: Titlebar menu button/popup (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-07-04 15:03 UTC by publiclyvisibleemail
Modified: 2023-07-04 19:45 UTC (History)
1 user (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 publiclyvisibleemail 2023-07-04 15:03:15 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  (Neon Unstable)  Login to an X11 session
2.  Switch the bottom bar to Task Manager, (default is Icons-only Task Manager)
3.  Unpin application shortcuts from Task Manager, (default: System Settings, Discover, Dolphin, Firefox)
4.  Confirm that they're gone.
5.  Reboot, (Meta+reboot+Enter)
6.  Login to an X11 session again.

OBSERVED RESULT
(At least) The four default application shortcuts are again pinned to the Task Manager, (/bottom bar).  If you unpin them again and reboot again, they'll show up again..  and again..

EXPECTED RESULT
If I unpin an application shortcut from Task Manager, (/bottom bar) I expect it to not show up again unless I specifically add it back.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.5.1

ADDITIONAL INFORMATION
Comment 1 publiclyvisibleemail 2023-07-04 19:32:09 UTC
And now the unpinned applications are finally gone, with a fourth or fifth reboot.  *shrug*
Comment 2 Nicolas Fella 2023-07-04 19:45:49 UTC

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