Bug 372003 - WM_CLASS issue in dolphin 15
Summary: WM_CLASS issue in dolphin 15
Status: RESOLVED UPSTREAM
Alias: None
Product: dolphin
Classification: Unclassified
Component: general (show other bugs)
Version: 15.12.3
Platform: Other Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-02 22:49 UTC by Fran
Modified: 2017-02-10 19:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fran 2016-11-02 22:49:52 UTC
In KDE4 it was possible set WM_CLASS to: WM_CLASS = "newname", "newname" by simply creating a link to the executable with the name of the desired class:

user@kde:~$ /usr/bin/dolphin4 -v
Qt: 4.8.7
Plataforma de desarrollo de KDE: 4.14.16
Dolphin: 14.12.3
user@kde:~$ ln -s /usr/bin/dolphin4 dolphin4-newname
user@kde:~$ ./dolphin4-newname  & xprop | grep WM_CLASS 
WM_CLASS(STRING) = "dolphin4-newname", "Dolphin4-newname"

This has stopped working in version 15:

user@kde:~$ /usr/bin/dolphin -v
dolphin 15.12.3
user@kde:~$ ln -s /usr/bin/dolphin dolphin-newname
user@kde:~$ /dolphin-newname  & xprop | grep WM_CLASS
WM_CLASS(STRING) = "dolphin-newname", "dolphin"
user@kde:~$ ./dolphin-newname --name dolphin-newname  & xprop | grep WM_CLASS
WM_CLASS(STRING) = "dolphin-newname", "dolphin"

The expected result:

WM_CLASS(STRING) = "dolphin-newname", "Dolphin-newname"

In other applications such as konsole the result is as expected.
Comment 1 Fran 2016-11-14 09:13:33 UTC
In konsole also does not work:

https://bugs.kde.org/show_bug.cgi?id=372441
Comment 2 Christoph Feck 2016-11-15 12:29:20 UTC
Does it work with pure Qt5 applications?
Comment 3 Fran 2016-11-15 22:18:01 UTC
(In reply to Christoph Feck from comment #2)
> Does it work with pure Qt5 applications?

I tried it with "QtCreator" and has the same problem.
Comment 4 Christoph Feck 2016-11-16 00:11:31 UTC
Then I suggest to report it the Qt developers via https://bugreports.qt.io/

It does not make sense to patch every application if it could be done centrally in Qt (e.g. xcb platform plugin).