nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Problem using InitialPixmapPlacement=2 (http://www.nvnews.net/vbulletin/showthread.php?t=115536)

spectred 06-28-08 01:16 PM

Problem using InitialPixmapPlacement=2
 
Hi all,

using InitialPixmapPlacemenet=2 I have the problem that every kind of desktop effects result in some kind of screen corruption.
For example the background of the kde4 (which is btw. without xgl unusable slow) logout screen only consists of parts of textures which were shown recently (e. g. if I would open a PDF document, close it an log out, parts of this document would be shown in the background).
Or when right clicking on a plasma workspace in kde4, for some seconds the menu appears as a corrupted area before it is shown correctly.
This also applies when logging into gnome with enabled compiz. After login parts of the wallpaper are drawn where they don't belong. This is fixed as soon as this part is drawn a second time.

Using a desktop without any effects (tested with kde3) I have no problems even using IPP=2.

Is this normal behaviour for IPP=2? (btw. GlpyhCache is also enabled but this doesn't seem to make any difference).
I am using an external monitor, maybe this could be relevant.

If I remember right these problems do not exist using xgl but I need proper OpenGl acceleration.

Systems specs:
GeForce 8600M GT (Driver version 173.14.05)
x server version 1.4.x

Thanks for every help.

spectred 07-02-08 12:36 PM

Re: Problem using InitialPixmapPlacement=2
 
2 Attachment(s)
Meanwhile I made a screenshot of the problem.
Bug report also attached.

kcrudup 07-03-08 12:25 PM

Re: Problem using InitialPixmapPlacement=2
 
FWIW, I get this, too- but only immedately after opening a new window and it clears up right away.

aos101 07-06-08 10:17 AM

Re: Problem using InitialPixmapPlacement=2
 
Quote:

Originally Posted by spectred (Post 1696928)
Or when right clicking on a plasma workspace in kde4, for some seconds the menu appears as a corrupted area before it is shown correctly.

I get this too, but it doesn't make any difference if I have desktop effects enabled or disabled (if anything it's worse with desktop effects enabled). I haven't tried playing about with InitialPixmapPlacement or anything. I did file a bug report at KDE wondering if it was anything they were doing:

http://bugs.kde.org/show_bug.cgi?id=164330

I'm running an FX 5200. I've found a few people with this problem, as mentioned in the KDE bug report.

spectred 07-07-08 07:21 PM

Re: Problem using InitialPixmapPlacement=2
 
Quote:

Originally Posted by aos101 (Post 1703622)
I get this too, but it doesn't make any difference if I have desktop effects enabled or disabled (if anything it's worse with desktop effects enabled). I haven't tried playing about with InitialPixmapPlacement or anything. I did file a bug report at KDE wondering if it was anything they were doing:

http://bugs.kde.org/show_bug.cgi?id=164330

I'm running an FX 5200. I've found a few people with this problem, as mentioned in the KDE bug report.

Well seems so. The issue with menus and windows is gone for me (hopefully for everyone, switched back from ubuntu to debian this weekend and after that it was gone :) )

btw. connected it to desktop effects because the problem only existed for menus on the plasma workspace and plasma seems to have always some kind of composite features.

Even the second problem (logout screen) is apparently not connected to nvidia.
http://bugs.kde.org/show_bug.cgi?id=164827

txf 07-08-08 01:59 PM

Re: Problem using InitialPixmapPlacement=2
 
This might have to do with qt4 argb textures and nvidia. there seems to be a ticket related to this on the qt bug tracker. Is the kde4 qt-copy argb enabled (plasma widgets transparent even without composting)?
Probably...This corruption disappears when compositing is enabled...

aos101 07-15-08 04:38 PM

Re: Problem using InitialPixmapPlacement=2
 
Quote:

Originally Posted by spectred (Post 1704882)
Well seems so. The issue with menus and windows is gone for me (hopefully for everyone, switched back from ubuntu to debian this weekend and after that it was gone :) )

The problem is still there for me in KDE4.1 RC1. I've noticed now the issue is also there with the open source nv dirver, so maybe it isn't a driver problem (or affects multiple drivers). Perhaps it is a Qt4 issue.

spectred 07-15-08 06:31 PM

Re: Problem using InitialPixmapPlacement=2
 
Quote:

Originally Posted by aos101 (Post 1713022)
The problem is still there for me in KDE4.1 RC1. I've noticed now the issue is also there with the open source nv dirver, so maybe it isn't a driver problem (or affects multiple drivers). Perhaps it is a Qt4 issue.

strange. Certainly they are not using the latest code from svn trunk to build the rc1 packages. Maybe the changes fixing this problem are not included in rc1. 9 days between the probable fix and the release of rc1. Just a guess :|

aos101 07-16-08 04:59 AM

Re: Problem using InitialPixmapPlacement=2
 
According to the schedule RC1 was tagged on July 8th, so presumably it included whatever code you were running. Strange.

spectred 07-19-08 09:09 AM

Re: Problem using InitialPixmapPlacement=2
 
Quote:

Originally Posted by aos101 (Post 1713671)
According to the schedule RC1 was tagged on July 8th, so presumably it included whatever code you were running. Strange.

You were right, the problem is still not fixed. It only worked for me using Debian. Tried again with Ubuntu and it is still there. strange...

jrusinek 07-30-08 03:14 PM

Re: Problem using InitialPixmapPlacement=2
 
I had artifacts with IPP=2 too. Changing to 1 helped.

I also heard that IPP=2 is problematic when using Cairo-based GTK engines, but I can't be sure if this is true...

changyp 01-14-09 12:02 PM

Re: Problem using InitialPixmapPlacement=2
 
I have this problem too..
I don't know how to solve it..


All times are GMT -5. The time now is 03:04 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.