Bug 188576 - Doesn't follow Xt's size hints
Summary: Doesn't follow Xt's size hints
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: metacity
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-11 13:00 UTC by Bastien Nocera
Modified: 2014-06-18 09:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-06 20:02:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
max_test.c (653 bytes, text/plain)
2006-04-11 13:00 UTC, Bastien Nocera 		no flags Details
metacity log for RHEL4 (250.86 KB, text/plain)
2006-04-11 13:02 UTC, Bastien Nocera 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 327543 0 Normal RESOLVED XSetWMNormalHints/PMaxSize: maximal bounds are not used optimally 2020-12-01 14:57:35 UTC

Description Bastien Nocera 2006-04-11 13:00:31 UTC 
Also upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=338073

1. Compile and launch the attached testcase
2. Maximise the window:
- metacity 2.8.6-2.8 (the current RHEL4) resizes to the full width and height of
the desktop
- metacity 2.14.0-1 (current FC5) doesn't resize the window at all and shows it
"maximised"
- WindowMaker, icewm and Blackbox work as expected (maximised state, 500x500 in
size).
Comment 1 Bastien Nocera 2006-04-11 13:00:32 UTC 
Created attachment 127611 [details]
max_test.c
Comment 2 Bastien Nocera 2006-04-11 13:02:35 UTC 
Created attachment 127613 [details]
metacity log for RHEL4
Comment 3 Søren Sandmann Pedersen 2006-04-11 16:16:52 UTC 
The RHEL 4 behavior is as it is by design, but the FC5 behavior is pretty
clearly a bug.
Comment 4 Bastien Nocera 2006-04-12 11:06:50 UTC 
Reassigning to Fedora to keep track of the upstream bug.
Comment 5 Søren Sandmann Pedersen 2006-09-06 20:02:03 UTC 
Upstream claims to have fixed this.
Note You need to log in before you can comment on or make changes to this bug.