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 661415 - Panel turns black when maximizing xfce4-terminal with nvidia graphics driver
Panel turns black when maximizing xfce4-terminal with nvidia graphics driver
Status: RESOLVED NOTGNOME
Product: vte
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-10-10 22:40 UTC by Lars Volker
Modified: 2011-10-12 13:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lars Volker 2011-10-10 22:40:27 UTC
Hallo,

when resizing the xfce4-terminal on Ubuntu Natty, parts of the screen turn black and only get updated when other windows are brought into foreground. Also when maximising the terminal, the xfce panel turns black. This only happens with the binary nvidia driver and only when compositing is *disabled*. 

A discussion of this issue is found on launchpad: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/777606

I have this issue myself, so please ask if I should provide further clarification or logfile output.
Comment 1 Christian Persch 2011-10-10 22:54:38 UTC
(In reply to comment #0)
> This only happens with the binary nvidia driver

We don't support the proprietary drivers. Use the free software drivers.

> and only when compositing is *disabled*. 

This is 'unity 2d', right? Try with metacity.
Comment 2 Lars Volker 2011-10-11 08:10:29 UTC
Hi Christian, thanks for you reply.

(In reply to comment #1)
> (In reply to comment #0)
> > This only happens with the binary nvidia driver
> 
> We don't support the proprietary drivers. Use the free software drivers.
Still this looks as a bug to me, which should be fixed. I could also somehow try to submit it to nvidia, if that might help.
> 
> > and only when compositing is *disabled*. 
> 
> This is 'unity 2d', right? Try with metacity.
This happens with xfce's own window manager xfwm4.
Comment 3 Christian Persch 2011-10-11 09:43:12 UTC
(In reply to comment #2)
> Hi Christian, thanks for you reply.
> 
> (In reply to comment #1)
> > (In reply to comment #0)
> > > This only happens with the binary nvidia driver
> > 
> > We don't support the proprietary drivers. Use the free software drivers.
> Still this looks as a bug to me, which should be fixed.

Yes, the bug is that you use the non-free drivers :-)

> > > and only when compositing is *disabled*. 
> > 
> > This is 'unity 2d', right? Try with metacity.
> This happens with xfce's own window manager xfwm4.

Do try with metacity, with compositing disabled. And also disable all ubuntu stuff (global menu, tiny scrollbars).
Comment 4 Lars Volker 2011-10-11 12:14:07 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Hi Christian, thanks for you reply.
> > 
> > (In reply to comment #1)
> > > (In reply to comment #0)
> > > > This only happens with the binary nvidia driver
> > > 
> > > We don't support the proprietary drivers. Use the free software drivers.
> > Still this looks as a bug to me, which should be fixed.
> 
> Yes, the bug is that you use the non-free drivers :-)
Doesn't everybody use nvidia-cards because the binary drivers are of better quality? I might have a look into the free drivers then.
> 
> > > > and only when compositing is *disabled*. 
> > > 
> > > This is 'unity 2d', right? Try with metacity.
> > This happens with xfce's own window manager xfwm4.
> 
> Do try with metacity, with compositing disabled. And also disable all ubuntu
> stuff (global menu, tiny scrollbars).
This happens with xfce, not gnome, so the ubuntu features have never been there (or I don't know them). I tried resizing the terminal window without compositing and with metacity, but with the same erroneous behaviour.
Comment 5 Christian Persch 2011-10-12 13:32:45 UTC
Since it only happens with the non-free driver, it's clearly a bug in the driver. Which we do not (and can not) support.