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 375713 - ICCCM initial_state == IconicState doesn't work
ICCCM initial_state == IconicState doesn't work
Status: RESOLVED DUPLICATE of bug 360900
Product: metacity
Classification: Other
Component: general
2.16.x
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2006-11-15 21:49 UTC by Olivier Fourdan
Modified: 2007-04-12 21:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Olivier Fourdan 2006-11-15 21:49:03 UTC
Please describe the problem:
it seems that 'initial_state ==
IconicState' is currently not working correctly in metacity (gnome 2.16
and current cvs).

For example, "xterm -iconic" shows mapped in metacity, while it didn't
in previous older versions of metacity.

It's a regression as metacity used to implement this properly in previous versions (e.g. metacity 2.8 had this working)

Steps to reproduce:
1. Run metacity
2. launch "xterm -iconic"
3. xterm starts mapped while it should start iconic


Actual results:


Expected results:
metacity should honor the ICCCM WM_STATE initial_state and start the application iconified when initial_state == IconicState

Does this happen every time?
Yes

Other information:
http://tronche.com/gui/x/icccm/sec-4.html
Comment 1 Bruno Boaventura 2006-11-17 23:18:00 UTC
I can confirm this bug here.
I will not confirm in bugzilla yet... let's wait the comments.
Comment 2 Elijah Newren 2007-04-12 21:40:55 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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