https://bugs.kde.org/show_bug.cgi?id=381266
--- Comment #5 from Kai Uwe Broulik <k...@privat.broulik.de> --- Yes, we changed something in 5.10, massively simplifying the mapping logic. In 5.9.5 we used some crude regular expressions to map the WM_CLASS to a .desktop file. In 5.10 we use StartupWMClass which, as you can see, fits, I don't know why it doesn't work. StartupWMClass=crx_pjkljhegncpnkpknbcohdijeoejaedia WM_CLASS(STRING) = "crx_pjkljhegncpnkpknbcohdijeoejaedia", "Google-chrome" We first try to apply the rules in taskmanagerrulesrc (which has none for Chrome in the file you posted, which is good) and after that the first thing we do is find a service with a mapping StartupWMClass. Can you run `find /usr/share/applications/ -name *.desktop | xargs grep StartupWMClass` and see if there's any Chrome/Chromium-related output? Also try running the same on ~/.local/share/applications - we first try to match StartupWMClass to the app name before we go to the window class. Maybe there's a spurious chrome .desktop file and it picks that one then. I don't have one here, but who knows ;) -- You are receiving this mail because: You are watching all bug changes.
