Ubuntu

Maximizing ignores docked panles with Xinerama

Reported by Haggai Eran on 2006-09-05
130
This bug affects 22 people
Affects Status Importance Assigned to Milestone
metacity
Confirmed
Low
compiz (Ubuntu)
Undecided
Unassigned
kdebase-workspace (Ubuntu)
Undecided
Unassigned
metacity (Debian)
Confirmed
Unknown
metacity (Ubuntu)
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: metacity

Hi
When I add another screen using Xinerama, the gnome panels remain in the first screen, which is great, but when the panel is aligned vertically near the border between the two screens (either on the right of the left screen, or on the left of the right screen), maximizing a window ignores the panel, and the window is maximized right to the edge of the screen.

Steps to reproduce:
1. Use xinerama with the second screen to the right of the first.
2. Add a vertical gnome panel to the right edge of the left screen.
3. maximize a window in the left screen.
4. The screen is maximized right to the edge of the screen, instead of the edge of the panel.

Changed in metacity:
status: Unknown → Confirmed
Sebastien Bacher (seb128) wrote :

Thanks for your bug. What version of Ubuntu do you use? Has pointed by Elijah that's known upstream as http://bugzilla.gnome.org/show_bug.cgi?id=339692

Changed in metacity:
assignee: nobody → desktop-bugs
importance: Untriaged → Low
status: Unconfirmed → Confirmed

thanks, I'm using ubuntu dapper.

Haggai

On 9/10/06, Sebastien Bacher <email address hidden> wrote:
> Thanks for your bug. What version of Ubuntu do you use? Has pointed by
> Elijah that's known upstream as
> http://bugzilla.gnome.org/show_bug.cgi?id=339692
>
> ** Bug watch removed: GNOME Bug Tracker #http://bugzilla.gnome.org/show_bug.cgi?id=339692
> http://bugzilla.gnome.org/show_bug.cgi?id=http://bugzilla.gnome.org/show_bug.cgi?id=339692
>
> ** Bug watch added: GNOME Bug Tracker #339692
> http://bugzilla.gnome.org/show_bug.cgi?id=339692
>
> ** Changed in: metacity (Ubuntu)
> Importance: Untriaged => Low
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Confirmed
>
> --
> Maximizing ignores docked panles with Xinerama
> https://launchpad.net/bugs/58977
>

--
Haggai Eran

Adam Bolte (boltronics) wrote :

I believe I am also experiencing this bug. I use two monitors using Xinerama, however they are positioned one on top of the other in a vertical layout.

When I have my GNOME Panel at the top of the bottom monitor, maximising a window on the bottom monitor hides the window titlebar behind the panel.

However, when I move the GNOME Panel to the top of the top monitor, maximising a window on the top monitor does not extend the window behind the GNOME panel.

I'm using Ubuntu Feisty, and have found reference to this bug on the GNOME website also:
http://bugzilla.gnome.org/show_bug.cgi?id=339692

elleP (pelle-quicknet) wrote :
Dave Gilbert (ubuntu-treblig) wrote :

yeh I'm seeing what sounds like the same as both of these;

two monitors stacked vertically; panels at the top and bottom of the top screen and bottom of the bottom screen.
If I hit maximize on a window on the top screen it is partially hidden by the bottom panel on the top screen.

This is on Interpid's beta as of today; metacity 1:2.24.0-0ubuntu1 with GL desktop off.

Dave

Dave Gilbert (ubuntu-treblig) wrote :

I've attached a hack/patch to gnome-panel for the bottom/vertical case of this to the gnome bug here:

http://bugzilla.gnome.org/attachment.cgi?id=127673&action=view

It's a nasty hack but it seems to work for the case I covered.

Dave

Conan (richard-connon) wrote :

I have the same problem with my screen setup:
1024x768+0+357
1680x1050+1024+75
1920x1200+2704+0
1280x1024+4624+0

It appears to be that more generally: maximising ignores any panel which is not at the extreme top, bottom, left or right of the entire virtual display.

Nick A (nickalleyne) wrote :

This affects me also.
It also does it with twinview which I was using previously to upgrading to Jaunty.

I agree with what Conan posted above, any non-extreme edge panel is ignored from my experience.

I am using a Dell D630 laptop with the main screen being the bottom.

I have attached a screenshot.

Conan (richard-connon) wrote :

Recent testing with all current updates suggests that for horizontal panels (that is ones at the top or bottom of a monitor) this bug only now occurs if the panel was put there since logon time.
Luckily this means that there is now at least a workaround for this bug (create and position all your panels, log off, log on, run other applications)

Nick A (nickalleyne) wrote :

really? that does not change it for me, I just restarted and it still does the same as in my screenshot above.

Conan (richard-connon) wrote :

Ah... I'm not actually using vertically stacked monitors. I just have some horizontal ones which aren't at the top or bottom extremes of the virtual desktop.

Seems this is more of an issue if there is another display above or below the panel in question...

Dave Gilbert (ubuntu-treblig) wrote :

Still does it on jaunty up to date as of today - note that a different change has caused some of the panels to move around.

Dave

Problem still persists on Karmic.

Changed in metacity (Ubuntu):
status: Confirmed → Triaged
Roland Neary (abcccc) wrote :

Problem still persists on Lucid.

Changed in metacity (Debian):
status: Unknown → Confirmed
Changed in metacity:
importance: Unknown → Low
Olivier Berger (olivierberger) wrote :

Hi.
Note that https://bugzilla.gnome.org/show_bug.cgi?id=583538 also seems related to that issue.

Helge (helgesdk) wrote :

I can also confirm this bug in Lucid.
LVDS: 1280x800
VGA: 1280x1024

Placing the monitors horizontally gives me a "deadzone" on LVDS because of the difference in resolution (see https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/373367).

Placing the monitors vertically causes maximized windows to overlap one of the horizontal panels.

Known issue in the panel.

On 12/12/10, Jakob Unterwurzacher <email address hidden> wrote:
> ** Also affects: compiz (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of compiz
> packagers, which is subscribed to compiz in ubuntu.
> https://bugs.launchpad.net/bugs/58977
>
> Title:
> Maximizing ignores docked panles with Xinerama
>
> _______________________________________________
> Mailing list: https://launchpad.net/~compiz
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~compiz
> More help : https://help.launchpad.net/ListHelp
>

--
Sent from my mobile device

Sam Spilsbury

Michel Filipe (mfilipe) wrote :

I find out a workaround but I'm using TwinView.

See: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/375503/comments/10

Dempf (amasover) wrote :

Do Compiz and Kwin need separate bugs filed against them?

Dempf (amasover) wrote :

Nevermind, forgive my noob comment :)

Sam Spilsbury (smspillaz) wrote :

The bug is in gnome-panel actually

Dave Gilbert (ubuntu-treblig) wrote :

It's more complicated than that; as I remember (from a couple of years ago when I posted the patch in #6 above) there are limitations in the 'strut' notification where a window tells the window manager to avoid an area; it can't really cope with an arbitrary area in the middle of the screen. So really it's a standardisation issue that the wm and panel need to understand; although heck knows if any of that has changed in the last couple of years.

Dave

Sam Spilsbury (smspillaz) wrote :

On Sun, Jan 30, 2011 at 10:27 PM, Dave Gilbert <email address hidden> wrote:
> It's more complicated than that; as I remember (from a couple of years
> ago when I posted the patch in #6 above) there are limitations in the
> 'strut' notification where a window tells the window manager to avoid an
> area; it can't really cope with an arbitrary area in the middle of the
> screen.  So really it's a standardisation issue that the wm and panel
> need to understand; although heck knows if any of that has changed in
> the last couple of years.

My understanding of the specification is that the strut notification
just says "avoid this area of the screen" as defined by
_NET_WM_STRUT_PARTIAL (since that allows you to specify the full
extents of the strut) [1]. So in that case the window manager should
not use that area for placement OR maximization. Of course, things get
tricky when you start considering snap-to, but I think in that case it
is reasonable to ignore the snap-to case where a strut does not share
an edge of the screen.

Both Compiz, Docky and Avant Window Navigator seem to follow this
mantra of doing things - the strut is set perfectly fine if you make
Docky adjacent to another screen edge.

Of course, the specification makes it clear that struts are only to be
used on screen edges and makes it doubly as clear that struts are not
to be reserved at the edge of Xinerama screens, but I haven't seen any
problems with allowing this. If you can point me to the discussion in
light of this bug, that would be much appreciated.

[1] http://standards.freedesktop.org/wm-spec/1.3/ar01s05.html

>
> Dave
>
> --
> You received this bug notification because you are a member of compiz
> packagers, which is subscribed to compiz in ubuntu.
> https://bugs.launchpad.net/bugs/58977
>
> Title:
>  Maximizing ignores docked panles with Xinerama
>
> _______________________________________________
> Mailing list: https://launchpad.net/~compiz
> Post to     : <email address hidden>
> Unsubscribe : https://launchpad.net/~compiz
> More help   : https://help.launchpad.net/ListHelp
>

--
Sam Spilsbury

AmenophisIII (amenophisiii) wrote :

unsurprisingly in maverick/10.10 the problem persists.

Changed in compiz (Ubuntu):
status: New → Confirmed
Changed in kdebase-workspace (Ubuntu):
status: New → Confirmed
Changed in compiz (Ubuntu):
status: Confirmed → Fix Committed
Olivier Berger (olivierberger) wrote :

Care to elaborate on what was fixed/how/where (version) regarding compiz in ubuntu ?

Harald Sitter (apachelogger) wrote :

Please report at bugs.kde.org.

Changed in kdebase-workspace (Ubuntu):
status: Confirmed → Invalid
Daniel van Vugt (vanvugt) wrote :

Sam, could you clarify the status of this bug?

This is still an issue in gnome-panel 3.8.0 while using Ubuntu 13.04 fallback mode.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.