Comments on: Screen redrawing problems with the “nvidia” driver and Compiz

By: marleo

marleo — Tue, 06 Oct 2009 01:35:37 +0000

Correction: still happening, but a lot less.

By: marleo

marleo — Tue, 06 Oct 2009 01:32:54 +0000

I’ve only noticed this problem in Firefox (and gecko-based browsers) so far. Going to about:config, changing mousewheel.withnokey.sysnumlines to false and changing mousewheel.withnokey.numlines to a value of 10 or more seems to fix it. Looks like, if enough of the screen changes, it will redraw it properly.

By: msanchez

msanchez — Mon, 16 Mar 2009 13:01:14 +0000

I’m so sorry to tell you, sHs, that no solution tried so far seemed to finally have got rid of the problem completely, as it seems it’s something related to the nvidia driver and compiz, not easy to fix though.

So, giving up using compiz will fix it but, if you don’t want to do it so, the only thing you can do is a combination of these tips and trying to use the latest “good” driver from nvidia, which so far are versions 173 and 177 (version 180 does not fall into the “good ones” as it get’s more trouble even than the glitches).

Another thing that also “helps-but-don’t-completely-fix” is to manually manipulate the /usr/bin/compiz shell script to use what they called ‘indirect rendering’. That is, to change the line:

# No indirect by default
INDIRECT=”no”

… into:

# No indirect by default
INDIRECT=”yes”

… in /usr/bin/compiz.

Hope this helps you somehow while we don’t find the definitive solution

By: shS

shS — Thu, 12 Mar 2009 08:19:54 +0000

msanchez: I’m running Gentoo, but you say that 173.14 fixes the problem?

What version particularly? I have .09, .12, .15 and .16 on portage.

By: msanchez

msanchez — Fri, 06 Mar 2009 22:14:34 +0000

shS: see my last update about using envy to get the v173 driver easily installed in your system if you’re still experiencing the same problem.

It worked for me (lately the same problem began to annoy me again)

By: J.A.

J.A. — Wed, 25 Feb 2009 14:08:12 +0000

Thanks!!

I’m suffering from this bug since months ago. Hope your fix will be solve the problem.

By: msanchez

msanchez — Wed, 25 Feb 2009 10:08:37 +0000

Hmmm.. perhaps your problem is different than mine then, since I’ve not experienced it again since that.

Anyway, all what I know about this nvidia setting is that it’s a temporary workaround for a bigger problem in the driver itself. Let’s hope that newer versions fix the problem (and I think they do, as I had not that problem when I had Ubuntu Intrepid installed)

By: shS

shS — Wed, 25 Feb 2009 09:56:34 +0000

Nope. It seems I still have this problem, but it appears more seldom. CTRL-ALT-F1 and coming back to X solves the problem temporarily.

By: msanchez

msanchez — Thu, 19 Feb 2009 13:08:46 +0000

> Thank you msanchez!
> I have NVIDIA Quadro NVS 140M and was struggling with this
> problem for a while now and your solutions seems to be
> working (so far no glitches).
>
> Thank you again.

You’re welcome. By the way, it is quite rewarding to see how a post is really helpful for someone else, so thank you too for let me know about it.

By: shS

shS — Thu, 19 Feb 2009 12:34:44 +0000

Thank you msanchez!
I have NVIDIA Quadro NVS 140M and was struggling with this problem for a while now and your solutions seems to be working (so far no glitches).

Thank you again.