Translations:LatteDock/FAQ/16/en: Difference between revisions

Revision as of 05:00, 11 April 2019

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (LatteDock/FAQ)

This issue means that plasma '''libtaskmanager''' has not associated your launcher and app windows correctly to the relevant desktop file. Plasma is trying to be smart enough in order to correctly identify which desktop files are associated to which specific windows, but there are cases when it fails. Best way to solve this is to check the <code>StartupWMClass</code> record in the desktop file. This record should point at the proper <code>WM_CLASS</code> record at all times. For example even though the Latte Dock desktop file is called {{Path|1=org.kde.latte-dock.desktop}}, its <code>StartupWMClass</code> is <code>lattedock</code>. In order to correctly identify the <code>StartupWMClass</code> of an application, you can use <code>xprop</code>.

That issue means that plasma libtaskmanager has not associated your launcher and app windows correctly to the relevant desktop file. Plasma is trying to be smart enough in order to correctly identify which desktop files are associated to which specific windows, but there are cases when it fails. Best way to solve this is to check the StartupWMClass record in the desktop file. This record should point at the proper WM_CLASS record at all times. For example even though the Latte Dock desktop file is called org.kde.latte-dock.desktop, its StartupWMClass is lattedock. In order to correctly identify the StartupWMClass of an application, you can use xprop.

Revision as of 17:10, 10 March 2019 (view source) FuzzyBot (talk \| contribs) (Importing a new version from external source)		Revision as of 05:00, 11 April 2019 (view source) FuzzyBot (talk \| contribs) (Importing a new version from external source) Newer edit →
Line 1:		Line 1:
	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 <code>StartupWMClass</code> record in the desktop file. ~~That~~ record should point at the proper <code>WM_CLASS</code> record at all times. For example even though Latte desktop file is called {{Path\|1=org.kde.latte-dock.desktop}} its <code>StartupWMClass<c/~~ode~~> is <code>lattedock</code>. In order to identify ~~correctly~~ the <code>StartupWMClass</code> ~~for~~ an application you can use <code>xprop</code> ~~to do so~~.		That issue means that plasma libtaskmanager has not associated your launcher and app windows correctly to the relevant desktop file. Plasma is trying to be smart enough in order to correctly identify which desktop files are associated to which specific windows, but there are cases when it fails. Best way to solve this is to check the <code>StartupWMClass</code> record in the desktop file. This record should point at the proper <code>WM_CLASS</code> record at all times. For example even though the Latte Dock desktop file is called {{Path\|1=org.kde.latte-dock.desktop}}, its <code>StartupWMClass</code> is <code>lattedock</code>. In order to correctly identify the <code>StartupWMClass</code> of an application, you can use <code>xprop</code>.