SUMMARY (Not a crash) Since KDE 6 update, icons-only taskbar behavior has changed. Pinned icons move around the list if launched, sometimes creating a duplicate icon for themselves. I have seen duplicate instances of an app running somehow and have not been able to reproduce that reliably. Sometimes, if something is launched another icon might disappear from the taskbar. More specifically: Most of my pinned icons are Google Chrome web apps. (examples are GMail, Google Calendar, Drive, a few other web apps for SaaS tools I use.) The pinned icon for Google Chrome most often disappears when launching one of these web apps. However, there are other things happening that are hard for me to track and observe as well. I unpinned and repinned these icons, I removed the applet and replaced it adding all the icons again, I've taken updates and restarted, I've looked at settings to see if any are relevant (doesn't appear so). Discover indicates I'm totally up to date. STEPS TO REPRODUCE (I had icons on it already, but it's the same if they are removed and added back) 1. Launch an application by single clicking an icon on task manager OBSERVED RESULT Observe strange behaviors: disappearing icons, icons jumping around, duplicate application instances etc. EXPECTED RESULT application launch with no other results SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Very similar to previously-resolved, year old bug 385594 launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around: https://bugs.kde.org/show_bug.cgi?id=385594
Created attachment 166481 [details] Screenshot of icon duplicate in this case, I launched an app and two Google Calendar icons are visible as a result. Sometimes, if one of the icons is clicked, it launches a different app whose icon is missing (as if the connection between what is visible and what is being launched has been broken)
Root cause looks to be the same as what's reported in Bug 475736. *** This bug has been marked as a duplicate of bug 475736 ***