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 527547 - Maximized windows below the panels using more than a monitor
Maximized windows below the panels using more than a monitor
Status: RESOLVED DUPLICATE of bug 339692
Product: metacity
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2008-04-11 14:04 UTC by Marco Barisione
Modified: 2008-04-11 18:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Marco Barisione 2008-04-11 14:04:43 UTC
When using a multi monitor setups maximized windows go below panels not placed at the border of a virtual screen.

To reproduce this without a multi monitor setup you can try this:
for i in `seq 1 4`; do Xnest :$i -ac -geometry 400x300+1+1 & done
Xdmx :10 -ac -configfile xdmx.conf +xinerama
export DISPLAY=:10
metacity
gnome-panel

Where xdmx.conf is:
virtual example {
    wall localhost:1 localhost:2
         localhost:3 localhost:4;
}

I think this happens because metacity asks for the _NET_WORKAREA property but this doesn't seem to include the space used by panels not on a border.
Comment 1 Elijah Newren 2008-04-11 14:36:22 UTC
I'm not familiar with Xdmx so I don't know where the panel is being placed (thanks for the tip, though, I'll have to give it a try at some point)...


Are you placing your panels in the middle of your monitor?  If so, what are we supposed to do in a case like that?  I don't even know what maximization should mean for such a case.

If you are placing your panels at the border of your monitor, between adjacent xineramas, then we have a separate bug about that and it's due to the fact that the EWMH hardcodes the available STRUT hints to be at the borders of the screen rather than allowing apps like the panel to specify the border of a xinerama.  It needs to be fixed in the EWMH first...)
Comment 2 Chris Lord 2008-04-11 14:53:03 UTC
This is a dup of bug #339692, I think
Comment 3 Elijah Newren 2008-04-11 15:05:44 UTC
Yes, if Marco is placing his panel at the edge of one of his monitors (thanks for tracking down the bug number, Chris!).  If Marco is placing his panel away from the edge of a monitor, then I want to know what he thinks maximization should mean.  Marco?
Comment 4 Marco Barisione 2008-04-11 16:18:13 UTC
My panel are placed at the top and at the bottom of the first monitor. The secondo monitor is placed below the first one:

------------------
XXXXXXXXXXXXXXXXXX     <- Panel


                       <- First monitor


XXXXXXXXXXXXXXXXXX     <- Panel
------------------

------------

                       <- Second monitor

------------

Metacity/gtk/whatever is pretty good at keeping windows in a single monitor (unless you want to move them between monitors), so I think that maximization should mean "use all the available space in the current monitor".

I'm closing this bug as a dup.

*** This bug has been marked as a duplicate of 339692 ***
Comment 5 Elijah Newren 2008-04-11 18:34:39 UTC
(In reply to comment #4)
> Metacity/gtk/whatever is pretty good at keeping windows in a single monitor
> (unless you want to move them between monitors), so I think that maximization
> should mean "use all the available space in the current monitor".

Yes, metacity has lots of logic to help ensure that.  I was just making sure that you weren't placing your panel in _the middle of a single monitor_, because then it wouldn't be possible to "use all the available space" without going under or over (or, using a non-rectangular window, around) the panel.
 
> I'm closing this bug as a dup.

Thanks.  :)