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 664858 - Screen repaint issues on nvidia native driver
Screen repaint issues on nvidia native driver
Status: RESOLVED DUPLICATE of bug 728464
Product: mutter
Classification: Core
Component: general
3.2.x
Other Linux
: Normal critical
: ---
Assigned To: mutter-maint
mutter-maint
: 650863 665527 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-11-26 04:12 UTC by Eugueny Kontsevoy
Modified: 2014-12-04 16:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
/var/log/Xorg.0.log (25.58 KB, text/plain)
2011-11-26 04:13 UTC, Eugueny Kontsevoy
Details

Description Eugueny Kontsevoy 2011-11-26 04:12:30 UTC
I am having screen repaint (invalidation) issues under Gnome3. I am not running in fallback mode, I am running "proper" Gnome shell with mutter.

The problem:
Some windows, notably gnome-terminal and gvim, do not always repaint themselves. Sometimes I'd type "ls" in terminal and won't see anything until I move the cursor around or force scrolling. 

Sometimes I'd run vim in gnome-terminal, close it but vim remains painted in terminal as if it was still running.

Sometimes, when typing (or moving around) in vim I get the wrong line of text painted in the wrong place. Again, moving the cursor or forcing refresh fixes it.

This seems to happen more often when the window is large. Maximized terminal windows are especially prone to it. 

When I try to take the screenshot of the corrupted windows, it comes out clean because the visual effect of the screenshot application causes the windows to repaint before it's taken.

Attaching my xorg.log file (nvidia driver info is there). Not sure which version of Gnome is it. It's 3.?? - how do I look it up? Nautilus reports its version as 3.2.1.

Some more info:
I have Thinkpad T510 laptop with Nvidia NVS 3100M card. 

I'm running the latest Ubuntu (11.09). 

$ uname -a
Linux t510 3.0.0-13-generic #22-Ubuntu SMP Wed Nov 2 13:27:26 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Comment 1 Eugueny Kontsevoy 2011-11-26 04:13:03 UTC
Created attachment 202167 [details]
/var/log/Xorg.0.log
Comment 2 Eugueny Kontsevoy 2011-11-26 06:07:07 UTC
I've been googling desperately trying to get the laptop in a workable state. Apparently there are other folks with the same issue:
http://ubuntuforums.org/showthread.php?t=1866709
Comment 3 Rui Matos 2011-11-26 14:39:06 UTC
Can you try with the latest nvidia driver? You can get it at http://www.nvnews.net/vbulletin/showthread.php?t=122606 .

If that doesn't help, testing with the nouveau driver can help to point where the problem is too.
Comment 4 Eugueny Kontsevoy 2011-11-27 05:30:28 UTC
The problem went away after upgrading to the latest nvidia driver.
Comment 5 Eugueny Kontsevoy 2011-11-28 02:19:03 UTC
Sorry I marked it as "OBSOLETE" too early. The problem still exists with the latest version 290.10 of native nvidia driver. It just happens less frequently. By the way I always had this issue with Compiz but there was a setting in Compiz (I believe) to fix this.

See, I asked this question a while ago (same hardware):
https://bbs.archlinux.org/viewtopic.php?id=110378

But the solution is offline now and I can't find it back.
Comment 6 László Monda 2012-01-20 22:22:54 UTC
I think this is the suckiest Gnome 3 bug of all!  It makes me want to pull my hair out!

Using both Gnome Terminal and Konsole is a miserable experience due to this bug.  I've tried these terminals under IceWM in which they worked perfectly.

https://bugzilla.gnome.org/show_bug.cgi?id=650863 and https://bugzilla.gnome.org/show_bug.cgi?id=665527 could be marked as duplicates of this bug.

(I'm not sure which should be the master bug (to which others reference) but the description of this bug is the cleanest of the three, I believe.)

Also, please visit https://www.google.com/search?q=gnome+3+terminal+redraw and after realizing that *it is* indeed a valid and pressing issue mark this bug "confirmed".

OS: openSUSE 12.1
Video card: GPU GeForce GTS 250M
Nvidia driver: 290.10-13.1
Mutter version: 3.2.1-2.1.2
Comment 7 Jasper St. Pierre (not reading bugmail) 2012-01-20 23:59:50 UTC
For you, then.

(We don't care about UNCONFIRMED vs. NEW, we treat them both the same. We're considering getting rid of one of them)
Comment 8 Jasper St. Pierre (not reading bugmail) 2012-01-21 00:00:53 UTC
*** Bug 650863 has been marked as a duplicate of this bug. ***
Comment 9 Jasper St. Pierre (not reading bugmail) 2012-01-21 00:01:22 UTC
*** Bug 665527 has been marked as a duplicate of this bug. ***
Comment 10 Jasper St. Pierre (not reading bugmail) 2012-01-21 00:02:51 UTC
Does running GNOME Shell like this fix the problem?

  CLUTTER_PAINT=disable-clipped-redraws gnoome-shell --replace
Comment 11 László Monda 2012-01-21 16:11:58 UTC
CLUTTER_PAINT did the trick but as a side effect it also screwed rendering in spectacular ways: windows flicker upon various actions like crazy (for example when Google Chrome loads a page or when exposing the dash by going to the upper left corner).

Moving to KDE until this gets resolved.
Comment 12 Gregory 2012-01-21 17:54:45 UTC
Tried this:
CLUTTER_PAINT=disable-clipped-redraws gnome-shell --replace

It makes the desktop unusable.
Comment 13 Jasper St. Pierre (not reading bugmail) 2012-01-21 22:22:36 UTC
Whoops, my bad. I thought disable-clipped-redraws disabled culling automatically. Try:

    CLUTTER_PAINT=disable-clipped-redraws:disable-culling gnome-shell --replace
Comment 14 László Monda 2012-01-22 19:59:44 UTC
Although

CLUTTER_PAINT=disable-clipped-redraws:disable-culling gnome-shell --replace

seems to make clutter correctly redraw terminal content, it happens with a significant delay, many times taking as long as about 1-2 seconds when scrolling a page within mcedit.

So far it's the best workaround for this bug but it's a far cry from having satisfying usability for terminals.
Comment 15 Jasper St. Pierre (not reading bugmail) 2012-01-22 23:55:29 UTC
Right, I just wanted to make sure it was related to clipped redraws. So the proper way to fix this bug would be to implement the NV_fence stuff.
Comment 16 Owen Taylor 2012-01-23 15:15:00 UTC
A month or so ago, I tried implementing the fence stuff and it did not fix serious update issues with gnome-terminal, which appeared to the best I could tell to be bugs in the nvidia X server. (Perhaps related to rendering on an ARGB window.) I didn't have a chance to do further testing at that point.
Comment 17 Owen Taylor 2012-01-23 20:50:51 UTC
(In reply to comment #16)
> A month or so ago, I tried implementing the fence stuff and it did not fix
> serious update issues with gnome-terminal, which appeared to the best I could
> tell to be bugs in the nvidia X server. (Perhaps related to rendering on an
> ARGB window.) I didn't have a chance to do further testing at that point.

So, the massive performance issues I was seeing with gnome-terminal and the nvidia proprietary drivers were with the 285.05.09 drivers; with 290.10, I don't see them any more - gnome-terminal performs very well. (Without fencing, but the Quadro FX 3700 I'm testing with here may be insufficiently multi-threaded internally to reveal problems.)
Comment 18 Gregory 2012-01-23 21:21:25 UTC
Actually, upgrading to 290.10 was the first thing I did when I started having the issue.  It didn't seem to help at all.  I mainly use urxvt with rgba transparency.  I tried xterm with plain black and white and it didn't seem to help either.
Comment 19 László Monda 2012-03-24 22:38:00 UTC
Gnome developers,

This bug makes the usability of Gnome 3 totally infeasible for a number of users who are heavy terminal users and who have some specific nvidia graphics cards.

I've just migrated to Linux Mint 12 and installed the latest nvidia driver only to find out that this bug still persists.

OS: Linux Mint 12
Video card: GeForce GTS 250M
Nvidia driver: 295.33
Mutter version: 3.2.1-0ubuntu2

It's a shame that the otherwise great Gnome 3 experience is totally negated by this bug.  As for now I have no choice but using XFCE as a viable alternative.

Just let me know if you wanna have a GeForce GTS 250 and I'll buy it for you or if you want me to donate specifically for this issue to be fixed.

It'd be very disappointing to see the next release of Linux Mint having this exact bug, leaving Gnome 3 useless.

Sigh...

PS: You may want to set the status of this bug to CONFIRMED and its severity to BLOCKER.
Comment 20 Jasper St. Pierre (not reading bugmail) 2012-03-25 06:29:02 UTC
It's not a blocker, as it won't be fixed before 3.4 release, and can't be: it's a mutual effort between the Clutter developers at Intel, and the nVidia driver developers. It will take some time. Use the CLUTTER_PAINT=disable-clipped-redraws:disable-culling hack as above. It turns out that nVidia's driver and the FOSS drivers do some things differently, and in order to fix the issues, we have to invent entirely new GL extensions:

  https://github.com/rib/gl-extensions/blob/master/GLX_EXT_buffer_age.txt

So hang in there.
Comment 21 Chris Prevoe 2012-06-27 12:28:15 UTC
I hate to be the noisy wheel, but has there been any motion on this?
Comment 22 Gregory 2012-09-15 02:45:48 UTC
It's been a while, Jasper.  Any update?

I'm curently using Fedora 17 with nvidia 304.37 and gnome-shell-3.4.1-5.fc17.i686
Comment 23 Henri Bergius 2012-09-19 15:38:46 UTC
Having the same issue with MacBook Air running Ubuntu 12.04 and GNOME Shell.
Comment 24 Lorenzo 2012-09-27 18:53:15 UTC
Same here, I still have this issue on Ubuntu 12.04.
Comment 25 drago01 2013-02-09 20:11:55 UTC
(In reply to comment #20)
> It's not a blocker, as it won't be fixed before 3.4 release, and can't be: it's
> a mutual effort between the Clutter developers at Intel, and the nVidia driver
> developers. It will take some time. Use the
> CLUTTER_PAINT=disable-clipped-redraws:disable-culling hack as above. It turns
> out that nVidia's driver and the FOSS drivers do some things differently, and
> in order to fix the issues, we have to invent entirely new GL extensions:
> 
>   https://github.com/rib/gl-extensions/blob/master/GLX_EXT_buffer_age.txt
> 
> So hang in there.

We got this now (clutter from git required). See bug 669122 . Will be in 3.8.
Comment 26 Mihails Strasuns 2014-06-20 20:05:06 UTC
I have a very similar issues with Gnome Shell 3.12.2 and nvidia 337.25 in Arch Linux. Is there any simple way to verify if this is indeed regression?
Comment 27 drago01 2014-06-20 20:09:18 UTC
(In reply to comment #26)
> I have a very similar issues with Gnome Shell 3.12.2 and nvidia 337.25 in Arch
> Linux. Is there any simple way to verify if this is indeed regression?

Probably this https://bugzilla.gnome.org/show_bug.cgi?id=728464
Comment 28 drago01 2014-06-20 20:09:50 UTC

*** This bug has been marked as a duplicate of bug 728464 ***