Bug 393793

Summary:	Can't correctly pin application desktop file for Quassel
Product:	[Plasma] plasmashell	Reporter:	Filipe Azevedo <pasnox>
Component:	Task Manager and Icons-Only Task Manager widgets	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	nate, plasma-bugs-null
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Other
OS:	Linux
URL:	https://bugs.quassel-irc.org/issues/1482
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	xprop quasselclient quasselclient desktop file

Description Filipe Azevedo 2018-05-03 08:00:40 UTC

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.

Comment 1 Eike Hein 2018-05-04 01:30:53 UTC

Please provide the following information:

- xprop output for the quassel window
- name of the correct quassel .desktop file and its contents

Comment 2 Filipe Azevedo 2018-05-07 19:31:16 UTC

Created attachment 112485 [details]
xprop quasselclient

Comment 3 Filipe Azevedo 2018-05-07 19:32:54 UTC

Created attachment 112486 [details]
quasselclient desktop file

Comment 4 Eike Hein 2018-05-08 06:06:41 UTC

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.

Comment 5 Filipe Azevedo 2018-05-08 07:40:50 UTC

Will reprot to quassel team, thanks.

Comment 6 Filipe Azevedo 2018-05-08 07:51:37 UTC

Done, https://bugs.quassel-irc.org/issues/1482

Comment 7 Filipe Azevedo 2018-07-16 20:06:20 UTC

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.

Comment 8 Eike Hein 2018-07-17 04:58:26 UTC

Which version of plasmashell are you using? StartupWMClass handling was improved a lot for 5.12.

Comment 9 Filipe Azevedo 2022-10-03 10:25:57 UTC

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.