Gnome panel bugs with secondary monitor

[h3]

Binary package hint: gnome-panel

If I create a new panel on my secondary monitory I can't add applets. At least they don't become visible in the panel, if I click randomly they are actually there, just not visible.

If I create it in my primary monitor and then add applets, everything works as expected. But if I drag the panel in my secondary monitor, icons freeze. They're still working, if I click on a window name it will raise it. But if I close the window it won't be removed from window list. Mouse over is broken too, it's really like if the panel becomes a static image.

So as soon as the panel is dragged into the secondary monitor, graphics stop to update.

I'm running Ubuntu Hardy with Compiz enabled

[Mackenzie Morgan (maco.m)]

What video card and driver are you using? Are you using 32 or 64 bit Ubuntu? Does this happen on all screen edges and with floating panels or only in certain positions? IMaybe the graphics card isn't properly redrawing the part of the screen into which the panel is being placed?

I can't reproduce this problem using Compiz, 32bit Hardy, and fglrx.

[h3 (h3)]

Kernel: 2.6.24-19-generic (32bit)
cpu: AMD64 4800
ram: 4G
gc: nVidia Quadro FX 1400
dual monitor setup: gxl, xinerama & twinview

Ok that just got weirder, I don't think it's a problem with the graphic card
redraw. I just did the following:

1. took my panel from the bottom of my first screen and dragged it to the
top of my second screen, the panel "froze"
2. I dragged it back to the bottom of my first screen, it was still frozen
3. I dragged the panel back to the top of my second screen BUT accidentally
dropped it on its left edge .. it started working back ..
4. I dragged it to the top .. and it's still working ..

I'll cross my fingers, but I have strong doubts that it will freeze back
soon enough..

2008/9/18 Mackenzie Morgan <email address hidden>

> What video card and driver are you using? Are you using 32 or 64 bit
> Ubuntu? Does this happen on all screen edges and with floating panels
> or only in certain positions? IMaybe the graphics card isn't properly
> redrawing the part of the screen into which the panel is being placed?
>
> I can't reproduce this problem using Compiz, 32bit Hardy, and fglrx.
>
> ** Changed in: gnome-panel (Ubuntu)
> Status: New => Incomplete
>
> --
> Gnome panel bugs with secondary monitor
> https://bugs.launchpad.net/bugs/271343
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Sebastien Bacher (seb128)]

thank you for your bug report, how do you configure your screens? do you get the issue every time? do you get any error in .xsession-errors when you get the bug?

[h3 (h3)]

> how do you configure your screens?

It's a dual monitor setup, I'm using Xinerama and nVidia Twin View with glx
enabled.

Here's the screen configuration in my xorg.conf:

Section "ServerLayout"
    Identifier "Default Layout"
    Screen 0 "Screen0" 0 0
EndSection

Section "Module"
    Load "glx"
EndSection

Section "ServerFlags"
    Option "Xinerama" "0"
EndSection

Section "Monitor"
    Identifier "Configured Monitor"
EndSection

Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "Acer AL1916W"
    HorizSync 30.0 - 82.0
    VertRefresh 56.0 - 76.0
EndSection

Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Acer AL1916W"
    HorizSync 30.0 - 82.0
    VertRefresh 56.0 - 76.0
EndSection

Section "Device"
    Identifier "Configured Video Device"
    Driver "nvidia"
    Option "NoLogo" "True"
EndSection

Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "Quadro FX 1400"
EndSection

Section "Device"
    Identifier "Videocard1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "Quadro FX 1400"
    BusID "PCI:1:0:0"
    Screen 1
EndSection

Section "Screen"
    Identifier "Default Screen"
    Device "Configured Video Device"
    Monitor "Configured Monitor"
    DefaultDepth 24
EndSection

Section "Screen"
    Identifier "Screen1"
    Device "Videocard0"
    Monitor "Monitor1"
    DefaultDepth 24
    Option "TwinView" "0"
    Option "metamodes" "DFP-1: 1680x1050_60 +0+0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Videocard0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "1"
    Option "TwinViewXineramaInfoOrder" "DFP-0"
    Option "metamodes" "DFP-0: 1680x1050_60 +0+0, DFP-1:
1680x1050_60 +1680+0"
EndSection

> do you get any error in .xsession-errors when you get the bug?

I've peeked in the system logs but did not find anything suspicious..

The bug does not seem to occur alone by itself.. I can reproduce it just by
dragging the panel from the top of my right screen
to the bottom of my left screen, from there it still works properly, but
when I drag it back to the top of my right screen it freeze
dead and became unusable.

However I've found a way to make it work again.. I just drag it to the left
side of my screen, in vertical position. From there
the window buttons starts working again and I can drag it back to its
original position and it still works..

I've done a tail -f on xession-errors while reproducing the bug, but I got
no errors message at all. I have the feeling that it
occurs when the panel is transfered from one screen to the other. I know
that xinerama is far from optimal and is probably
the culprit, but it's the only way I can get the windows to behave
"normally" (like not maximizing over both monitors).

I hope it will help

regards

2008/10/2 Sebastien Bacher <<email address hidden>...

[Sebastien Bacher (seb128)]

could somebody having a similar configuration send the bug to bugzilla.gnome.org where the people writting the software will read it?

[Sebastien Bacher (seb128)]

does anybody still get the issue and could send the bug to GNOME?

[h3 (h3)]

I can confirm that this bug is also reproducible on Intrepid Ibex.

And I filled the bug report for gnome:
http://bugzilla.gnome.org/show_bug.cgi?id=562603

regards

2008/11/28 Sebastien Bacher <email address hidden>

> does anybody still get the issue and could send the bug to GNOME?
>
> --
> Gnome panel bugs with secondary monitor
> https://bugs.launchpad.net/bugs/271343
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[xoddam (jonathan-xoddam)]

I just upgraded to Jaunty and saw this problem for the first time.

I'm on x86_64 (a Dell XPS M1330)
I have gnome-panel 1:2.26.0-0ubuntu7
I have nvidia driver 180.44

Old behaviour: In Intrepid (same nvidia driver, no idea what gnome-panel version) both panels would sit on whichever monitor I told the nvidia-settings applet to use as the primary X display and they would behave the same as they do with a single monitor.

In Jaunty, if I enable a second monitor, the top panel goes on whichever display is primary and the bottom panel on the secondary. The top panel with the clock, launchers and notifiers then ceases to be redrawn, wherever try to drag it. I was late to a meeting because the clock was frozen!

Disabling either display does not cause it to recover: only logging out and in again will do that. I haven't yet tried starting a new X session with both displays already enabled (too much going on in this one).

[xoddam (jonathan-xoddam)]

Workaround: ensure one screen is definitely specified as 'primary' in the nvidia-settings panel, then 'killall gnome-panel' after applying changes and quitting nvidia-settings. The gnome-panel process is restarted with both panels on the primary screen and is correctly redrawn.