Red Hat Bugzilla – Bug 198982
aiglx+composite is enabled by default, but does not work with GForce 7600 GS
Last modified: 2007-11-30 17:11:37 EST
Description of problem:
On an x86_64 ck804 system, with a 7600 GS, nv driver in exa mode xorg
blue-screens by default in rawhide
disabling composite in xorg.conf recovers the display but kills metacity
trying to disable aiglx in serverlayout is an instant-reboot one xorg is launched
what poor nv users like me are supposed to do in the brave new aiglx world ?
Ok, more analysis: like a lot of people I had tried aiglx in the past before
deciding it was not for me. So I hade the use-composing entry in my metacity
It was inactive for months
Then composing is forced on by default. And even after setting the composing
extension to off, metacity still tries it and crashes if it's not active.
Metacity should fallback transparently to non-composing on an xserver with
composing disabled intead of leaving the user with no window manager
Moving the metacity part to bug #199055 to keep only the aiglx+compose part
Also, are you using the 32bit OS, or 64bit x86_64 OS?
More investigation shows the problem only occurs when the gconf key for
composing is on in metacity (apps/metacity/general/composing_manager):
- with normal xorg.conf -> blue screen in user session
- with normal xorg.conf + AIGLX off -> blue screen in user session, reboot in
gdm after trying to switch to-and-from console a few times
- with normal xorg.conf + composing off -> no blue screen, metacity dies in the
user session with:
Window manager warning: Log level 16: Disabling compositor since the server is
missing at least one of the COMPOSITE, DAMAGE, FIXES or TEST extensions
Erreur de segmentation
Created attachment 132916 [details]
normal system xorg conf
Created attachment 132917 [details]
xorg log when bluescreening winth composing on in metacity
AIGLX off is just putting Option "AIGLX" "Off" in ServerLayout
I don't have the logs for the reboot case
We're going to disable the metacity compositor for FC6, but the same thing might
happen with compiz.
Have you tried compiz? Do you know if the same thing does happen?
Need to wait next week-end before I try something as invasive as changing the
The "metacity" compositor "gconf" key never got enabled unless the user decided
deliberately to do so!
Reporter, I see at least two bugs in this report:
- Disabling AIGLX in config file makes machine reboot when X starts
- Compositor (compiz now) fails aggressively on nv hardware
Are you still seeing either one of these failures?