openjdk team mailing list archive
-
openjdk team
-
Mailing list archive
-
Message #09251
[Bug 751909] Re: Java Swing applications displayed with wrong name
** Changed in: bamf
Importance: Undecided => Medium
** Changed in: unity
Importance: Undecided => Low
** No longer affects: unity-2d
** Changed in: bamf
Status: Confirmed => In Progress
** Changed in: unity
Status: Confirmed => In Progress
** Changed in: unity
Importance: Low => Medium
** Changed in: bamf
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: unity
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: unity
Milestone: None => 7.1.0
--
You received this bug notification because you are a member of OpenJDK,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/751909
Title:
Java Swing applications displayed with wrong name
Status in BAMF Application Matching Framework:
In Progress
Status in Unity:
In Progress
Status in “bamf” package in Ubuntu:
Confirmed
Status in “openjdk-6” package in Ubuntu:
Confirmed
Status in “openjdk-7” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: unity
On launcher, all Java Swing applications are with wrong name. Their
tooltip shows the Java class name, with the dots changed by hiphens.
For example, Netbeans icon itself gets inactive after startup.
Then an icon with a '?' shows up indicating "java-lang-Thread" on mouseover.
------------------------------------------------------------------------------------------
Treviño: this issue is java related (affecting javaws apps as well) and it's caused by the fact that the Java apps doesn't correctly set the WM_CLASS X property on their windows. There was a bug for it (including a patch): http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6528430
The ubuntu java package should probably include it.
A workaround to fix it is to use this window matching agent: https://github.com/jelmerk/window-matching-agent then you need to update the application
.desktop file to change the Exec value including -javaagent:agent.jar=<AppWMClass> and adding StartupWMClass=<AppWMClass>.
To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/751909/+subscriptions