openjdk team mailing list archive
-
openjdk team
-
Mailing list archive
-
Message #09292
[Bug 751909] Re: Java Swing applications displayed with wrong name
This bug was fixed in the package bamf - 0.5.0+13.10.20130717-0ubuntu1
---------------
bamf (0.5.0+13.10.20130717-0ubuntu1) saucy; urgency=low
[ Marco Trevisan (Treviño) ]
* BamfApplication: keep track of the application main-window and
update name and icon accordingly Applications without a .desktop
file should update their name and icon based on their children. So
now we try to compute the main window children, and we update name
and icon based on it. (LP: #751909)
[ Ubuntu daily release ]
* Automatic snapshot from revision 564
-- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx> Wed, 17 Jul 2013 02:01:42 +0000
** Changed in: bamf (Ubuntu)
Status: In Progress => Fix Released
--
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:
Fix Committed
Status in Unity:
Fix Committed
Status in “bamf” package in Ubuntu:
Fix Released
Status in “openjdk-6” package in Ubuntu:
Confirmed
Status in “openjdk-7” package in Ubuntu:
Confirmed
Status in “unity” package in Ubuntu:
Fix Released
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