|
|
#1 | |
|
Registered User
Join Date: Mar 2006
Posts: 6
|
Hi everybody!
I use Ubuntu Breezy on a machine with a Geforce FX 5200 videocard and things have been running smoothly for the most part. I just upgraded the drivers to 1.0-8756 and things seemed alright at first, but tghen I noticed screensavers don't work properly when transparency is enabled for windows. All I see are a few bits and pieces of the screensaver, running with like 2 fps, on areas of the screen that corespond to where transparent windows are. My desktop environment is Gnome, configured to run kwin as a window manager, instead of metacity, partly because setting transparencies is easier. This has worked without problems with drivers before this one. Probably some info from lg files is needed to help me, but I dunno which one(s). Can anybody help? EDIT: forgot to mention, if needed, that screensavers run perfectly when transparencies are disabled |
|
|
|
|
|
|
#2 | |
|
NVIDIA Corporation
Join Date: Mar 2005
Posts: 2,487
|
Hi Louis,
Which version of X are you using? GLX with Composite is only designed to work correctly with X.org 6.9 and higher. -- Aaron |
|
|
|
|
|
|
#3 | |
|
Registered User
Join Date: Mar 2006
Posts: 6
|
Quote:
![]() Indeed, xorg under Breezy is only 6.8. So you're saying that thing working fine with previous versions of the driver was just luck? In this case, is upgrading Xorg a guaranteed solution to this? Well... I'd start using Dapper testing rather than compiling X, but it's good to know.... |
|
|
|
|
|
|
#4 | |
|
NVIDIA Corporation
Join Date: Mar 2005
Posts: 2,487
|
Quote:
|
|
|
|
|
|
|
#5 | |
|
Registered User
Join Date: Mar 2006
Posts: 6
|
Quote:
Ok, thanks. I understand. (and I actually remember the flickering) ![]() |
|
|
|
|
|
|
#6 | |
|
Registered User
Join Date: May 2005
Posts: 55
|
I wouldn't go an blame the issue on Xorg; however, that is a pretty old version.
I am running version 7 and with composite enabled, the OpenGL screen savers in KDE, UT2004, and some other OpenGL stuff is broke. I have already posted this issue, and there is a bug report in for it; the Nvidia people were able to re create the issue. Problem is with the driver for the most part and we are still waiting for a fix ![]() If there are testers needed for a patch, I would be glad to assist... Joe |
|
|
|
|
![]() |
| Thread Tools | |
|
|