Created attachment 145832 [details] Two icons for Chrome can be seen SUMMARY If Google Chrome has flags enabled, the Icons-Only Task Manager will sometimes not properly group the application, as the flags cause Plasma to believe it is a separate program STEPS TO REPRODUCE Unfortunately the exact trigger for the bug is unknown, though I have noticed it arising from running Google Chrome with various flags enabled using an auxiliary chrome-flags.conf placed at ~/.config . OBSERVED RESULT Two copies of Google Chrome are created in the taskbar EXPECTED RESULT The Google Chrome icon combines properly SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.8.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Relevant line in the file plasma-org.kde.plasma.desktop--appletsrc : launchers=applications:google-chrome.desktop,applications:google-chrome --enable-features=VaapiVideoDecoder --use-gl=desktop.desktop,applications:steam.desktop,applications:signal-desktop.desktop,preferred://filemanager,applications:org.kde.konsole.desktop (Normally the second icon appears unpinned and will not be in this file; in order to investigate this bug I manually pinned the duplicate which led me to discover this anomaly) Contents of ~/.config/chrome-flags.conf : --ignore-gpu-blocklist --enable-gpu-rasterization --enable-zero-copy --enable-features=VaapiVideoDecoder --use-gl=desktop
Created attachment 145833 [details] Place this in ~/.config
Is that on X11 or Wayland?
Can you please hover over the second entry and make a screenshot of the popup?
(In reply to Nicolas Fella from comment #2) > Is that on X11 or Wayland? X11.
(In reply to Nicolas Fella from comment #3) > Can you please hover over the second entry and make a screenshot of the > popup? As noted before the bug happens randomly, but I'll grab a screenshot once it occurs. Although for the record, visually on the end user side there was nothing out of the ordinary; the popup simply showed thumbnails just like any other icon.
*** This bug has been marked as a duplicate of bug 358277 ***