After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 131816 - Bad Behavior when WM_ICON_NAME is not defined for window
Bad Behavior when WM_ICON_NAME is not defined for window
Status: RESOLVED DUPLICATE of bug 124463
Product: libwnck
Classification: Core
Component: general
2.4.x
Other Linux
: Normal minor
: ---
Assigned To: libwnck maintainers
libwnck maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-18 01:37 UTC by gavrilao
Modified: 2007-04-30 18:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description gavrilao 2004-01-18 01:37:43 UTC 
IMHO when WM_ICON_NAME is not defined taskbar should display the string in
WM_NAME, so to make work better even apps that are not full supporting
standards.

For example eterm does'n set WM_ICON_NAME so if I open vorious istances of
eterm, I can't read on taskbar what process is running into each one.

REgards
Comment 1 Vincent Untz 2004-02-24 15:35:36 UTC 
This is a bug in libwnck.
Comment 2 Kjartan Maraas 2004-04-18 21:53:09 UTC 
There's a patch to change it so that it just uses WM_NAME instead of
WM_ICON_NAME in here. Maybe this should be marked as a duplicate?
Comment 3 Elijah Newren 2004-10-19 22:27:06 UTC 
For reference, that other bug is bug 124463.  I'm guessing it's a duplicate...
Comment 4 Vincent Untz 2007-04-30 16:52:09 UTC 
I'm lost because if WM_ICON_NAME isn't set, wnck_window_get_icon_name() returns WM_NAME and has always done so. Maybe WM_NAME wasn't set either? We're now returning a fallback name if none of them are set, but we didn't do so before.
Comment 5 Elijah Newren 2007-04-30 18:20:39 UTC 
Let's just mark this as a dupe of 124463, which was fixed mid-2005.

*** This bug has been marked as a duplicate of 124463 ***