I'm a quassel-client user (and only client, not the full monolithic quassel application). When I want to pin it in the taskbar it does not works, instead it pin the normal full monolithic application. If I then tweak the plasma settings file to fix the pined desktop file for quassel and restart it correctly show the desired application, still clicking it will add a new desktop entry because the taskbar thing the just launched application is not the pined one. I did not noticed another application being broken, but quassel is one of the only one providing the same application in 2 different implementation.
Please provide the following information: - xprop output for the quassel window - name of the correct quassel .desktop file and its contents
Created attachment 112485 [details] xprop quasselclient
Created attachment 112486 [details] quasselclient desktop file
It's an app bug - the second part of WM_CLASS is 'quassel' when it should be 'quasselclient' to match the .desktop file name. Alternatively the .desktop file could contain StartupWMClass=quassel, but it doesn't either. You could use taskmanagerrulesrc to add a custom mapping to work around this, but preferrably you should report it to Quassel for them to fix it.
Will reprot to quassel team, thanks.
Done, https://bugs.quassel-irc.org/issues/1482
Eike: I did tested yur trick to add "StartupWMClass=quassel" - does not works. That still pin the WRONG desktop file. I want to emphasize that the issue is really the wrong desktop file being pinned, not the wrong binary launched by the pined desktop file.
Which version of plasmashell are you using? StartupWMClass handling was improved a lot for 5.12.
sorry, looks like I forget to answer here at the time... I'm using 5.25.5 by now and still get the issue. I reported the issue upstream and they said (at the time, no idea now) that they will not change it, because *it's to share the settings between the 2 applications* I will try again the workaround you pointed before.