|
|
#1 | |
|
Registered User
Join Date: Oct 2008
Posts: 7
|
Hi,
Running Fedora 12 and KDE. I've got the latest nvidia driver installed... 195.36.15 I think I have a good xorg.conf but I can't get KDE to allow "Enable desktop effects". The Compositing State always shows "Compositing is disabled". What do I need to do to get this working? Thanks |
|
|
|
|
|
|
#2 | |
|
NVIDIA Corporation
Join Date: Mar 2005
Posts: 2,487
|
According to your log file, Composite is enabled just fine. Does xdpyinfo show "Composite" in the extensions section? If so, something is probably broken inside KDE.
|
|
|
|
|
|
|
#3 | |
|
Registered User
Join Date: Oct 2008
Posts: 7
|
Quote:
In reading Chapter 23 of the driver's README it states that compositing will be disabled if XINERAMA is enabled. So, if that is what is happening, then how do I stop XINERAMA from being enabled? |
|
|
|
|
|
|
#4 | |
|
NVIDIA Corporation
Join Date: Feb 2010
Location: Santa Clara, CA
Posts: 237
|
You already have
Option "Xinerama" "0" in ServerLayout, which should do it. Actually, scrolling further down, you also have it in "Extensions". Try changing the line in Extensions to read Option "Xinerama" "Disable" instead. |
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Dec 2005
Posts: 26
|
Hi, I have a user on frugalware that faced the same problem. And for which I already tried to disable various extensions without success.
Reverting to xorg-server 1.7.5 solved the problem, so it seems to be related to one of the patch introduced for 1.7.6. But I was not able to track the culprit yet. |
|
|
|
|
|
#6 | |
|
Registered User
Join Date: Oct 2008
Posts: 7
|
Quote:
I tried you suggestion.... Same results. FWIW, nvidia-xconfig was the process that generated Option "Xinerama" "0". |
|
|
|
|
|
|
#7 |
|
Registered User
Join Date: Jun 2004
Posts: 50
|
You thought right, it's just developers are too lazy to fix the driver.
|
|
|
|
|
|
#8 | |
|
Registered User
Join Date: Oct 2008
Posts: 7
|
Quote:
xorg-x11-server-Xorg-1.7.1-7.fc12.i686 xorg-x11-server-common-1.7.1-7.fc12.i686 Didn't fix the problem... But, maybe other packages need to be downgraded as well.... I may go ahead and reinstall with all the older xorg packages to see if it fixes the issue.... Takes time, but this is a new clean install... |
|
|
|
|
|
|
#9 |
|
Registered User
Join Date: Jun 2004
Posts: 50
|
Downgrade to 1.6.XX and check again.
|
|
|
|
|
|
#10 |
|
Registered User
Join Date: Oct 2008
Posts: 7
|
|
|
|
|
|
|
#11 |
|
Registered User
Join Date: Dec 2005
Posts: 26
|
For me it's a shot in the dark, else it would have been reported earlier.
|
|
|
|
|
|
#12 | |
|
Registered User
Join Date: Oct 2008
Posts: 7
|
Quote:
I have found that F12 is running xorg 1.7, which according to the release notes of X11R7.5 they are equivalent. OpenSuse 11.2 is running X11R7.4 which equates to 1.5. I just installed OpenSuse 11.2 and all is well. What a pain. Looks like I have to decide between distros and see which one has the features that mean the most to me....and wonder if I stick with OpenSuse won't the same issue pop up at a later date when they update the xorg server. Thanks.... |
|
|
|
|
![]() |
| Thread Tools | |
|
|