Translations:LatteDock/FAQ/16/en
That issue means that plasma libtaskmanager has not associated correctly your launcher and app windows with the relevant desktop file. Plasma is trying to be smart enough in order to identify correctly which desktop files are associated to specific windows but there are cases that it fails. Best way to solve this is to check the StartupWMClass
record in the desktop file. That record should point at the proper WM_CLASS
record at all times. For example even though Latte desktop file is called org.kde.latte-dock.desktop its StartupWMClass<c/ode> is
lattedock
. In order to identify correctly the StartupWMClass
for an application you can use xprop
to do so.