[nvidia-glx] glitches appear when using Twinview with compiz/beryl and the gnome-panel at the top is not set to "expand"

Bug #106691 reported by eppy 1
4
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I'm using the Nvidia-glx package with Twinview on a Geforce Ti 4200.

If I set my gnome-panel that's oriented to the top, and uncheck "Expand" under Panel Properties (by right clicking on a panel empty space), then I get graphical errors that go all across the top of the gnome-panel, and even on the second monitor (with Twinview) there's space reserved for the gnome-panel which there shouldn't be.

Revision history for this message
eppy 1 (choppy121212) wrote :
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thanks for your bug report.

eppy 1:
I've noticed the different colouring in your taskbar. Is your Ubuntu install heavily customised with third party packages? Are you using Feisty's beryl/compiz/xorg or are you using them from another repository? Can you reproduce this problem on a single monitor setup?

Revision history for this message
eppy 1 (choppy121212) wrote :

Oh yes, I'm using Gimmie (sudo aptitude install gimmie) which is the different colored menus. It's an applet for gnome-panel.

The only third party package is the nvidia binary drivers (even that from the Feisty repos)-- everything else is Feisty Fawn.

I will try to reproduce it on a single monitor with the nvidia drivers. Thanks for responding :)

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

If you are getting the nvidia module via the Fesity repos then that's not going to invalidate this bug.

I'm not quite sure as to where this bug should go.... If it is reproducible with the open source nv driver on a single monitor then I would guess its a xorg bug otherwise it is most likely a bug in the nvidia binary driver. The incorrect empty space might be a symptom of the way Twinview is presenting its screens but could just as likely be a bug in gnome-panels that aren't using expand on differently sized monitors...

Revision history for this message
eppy 1 (choppy121212) wrote :

Update: for me, it only happens with Twinview (two monitors) with the nvidia binary driver. I don't know if it would happen with Xinerama on the nv drivers.

BTW I really choose not to select expand because otherwise, the gnome-panel would stretch across both screens which I guess is a bug in Gnome.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

eppy 1:
Do you still see the glitches when you are not using compiz/beryl?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

(btw: I don't think the nv driver supports dual head in any form at the moment)

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Punting from Ubuntu -> linux-restricted-modules-2.6.20 because this will only be reproducible with the binary driver.

Revision history for this message
eppy 1 (choppy121212) wrote :

Hmm. On a single monitor with nvidia, I don't see glitches, but the whole top of the screen (where one my panels NOT expanded is) is "locked", so I can't start making a drag selection box on the desktop from that position. When I turn Beryl on, it just goes black, and then I start getting glitches if I move windows across it. With Twinview, I get the glitches on both monitors across the top.

It seems like a weird combo of the nvidia drivers and gnome-panel.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

eppy 1:
I'm not exactly clear on this. Are you saying that the glitchiness is only visible when beryl is turned on regardless of whether Twinview is in use or not?

Revision history for this message
eppy 1 (choppy121212) wrote :

Yes it was, weirdly enough-- Just now though, I figured out that it's because my monitors were set at two different resolutions (they're different sized monitors). If I set them at the same resolution, than everything is normal.

It seems to be gone or at least usable until/if Nouveau works on my card, so I guess you can reject this bug...and thanks for all your help and responses here.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Setting back to unconfirmed. It's probably better if we leave this open to increase the chances of other people with the same problem finding out why it happens...

Changed in linux-restricted-modules-2.6.20:
status: Needs Info → Unconfirmed
Revision history for this message
Bryce Harrington (bryce) wrote : linux-restricted-modules-2.6.20 is obsolete

This package has become obsolete so we're closing out the bug report as WONTFIX.
Thanks for reporting it though!

Changed in linux-restricted-modules-2.6.20:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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