https://bugs.kde.org/show_bug.cgi?id=396871
--- Comment #26 from Eike Hein <h...@kde.org> --- It's quite OK and expected for the two components of WM_CLASS to be substantially different. In general the relevant one for identification purposes is only the second string, which should match a .desktop file name or the value of a .desktop file's StartupWMClass key (the Task Manager also tries many other things to identify apps beyond that, if apps get this wrong). The issue with LO6 is that this second string changes during startup from something generic no .desktop file exists for (and that doesn't match the launcher) to the eventual one that does. -- You are receiving this mail because: You are watching all bug changes.
