latest xorg security update breaking compiz fusion

Has anyone else experienced this issue with the latest xorg security update ? It completely broke my compiz fusion. Its now saying:

AttributeError: Environment instance has no attribute ‘glx_vendor’

NVIDIA modules are their glx, composite, and other options are in the xorg.conf but compiz wont load now…

really makes you want to think twice before updateing anything anymore

Xorg updates often change the driver ABI, and break the ATI and NVIDIA drivers. ATI and Nvidia need to constantly change the drivers to match the Xorg ABI.

Try reinstalling your Nvidia driver then reboot. The Xorg upgrade breaks a symbolic link that will be reinstated by the install.

> Xorg updates often change the driver ABI, and break the ATI and NVIDIA
> drivers. ATI and Nvidia need to constantly change the drivers to match
> the Xorg ABI.

wouldn’t it be cool if they could talk beforehand, and have a match ready??


thanks for the tip ! Just like you said it removed the symbolic link from … no wonder … I was pulling my hair out with python config files and X11 / compiz-fusion configs,

Also thanks @ everyone else for your quick replies


AMD/ATI is working towards greatly improving the open source driver. I believe they intend to open up the driver as much as possible. They license some stuff from other vendors that they don’t have permission to release. The open radeon driver can be updated the second Xorg is updated. Proprietary drivers only come out when ATI and Nvidia feel like releasing drivers. So sometimes an Xorg update comes out, and you can’t run the latest Xorg with the proprietary drivers for months.

Sorry to bring this back up, but after fixing the issue I decided to report it to bugzilla as I felt I wouldnt be the only one with this issue here is the reply I got from novell.

— Comment #1 from Stefan Dirsch 2008-06-15 08:39:34 MDT —
Obviously you installed the NVIDIA driver manually instead of using the
prebuilt NVIDIA driver RPMs available for openSUSE 10.3. We do not support such
a scenario. We’re not responsible for a driver, which manual installation
replaces half of the X window system. I’m sorry.

It seems novell / opensuse is only supporting the 1 click installers ? Can anyone confirm this ?

I am sorry but I really think this is a poor attitude to take towards a community. First rollout a patch , break a desktop , then to say the issue wont even be looked into because your constellation is not supported ?? I am sure I am not the only one who doesn’t install my drivers per “one click”

I don’t understand the problem here. I don’t use “one click”, and I’ve never been forced to use it. Simply add the repos where the rpm is located, to your package manager.

One way to do this is to go to webin, do a search on the rpm, location the repository/server, and add it to your repos.

Or instead of adding the rpm to your repos, simply download the rpm (from the web site identified in my sentence above) to your hard drive, and install it with zypper, smart, rpm command, or what ever.

What am I missing here?

I doubt the claim that a manual Nvidia driver install updates “half of the X window system”. I suspect a repository install does much the same as a manual install.

The Novell approach (ie driver modules in a repository) probably works for most people, and does have the advantage of dependency matching when other X components are updated. So long as all your X window stuff is sitting in (supported) Novell repositories.

That is, update xorg and theoretically the dependent Nvidia module is updated seamlessly.

However, for stability reasons I guess, the Nvidia modules in the larger public repositories tend to lag behind the manually installable versions, and you don’t get as many choices if something is not quite working, particularly so when kernels, Xorg, Compiz, openGL, your DM and Nvidia driver are subject of independent development. Furthermore, not all hardware configurations are the same. Welcome to open source - flexible, adaptable, because it is not sold with hardware.

My experience has been positive with manual installs, and negative with repository installs, for the above reasons. If I were you I would stay with the manual option, and simply re-install as a first option should an update break something. I keep a few recent Nvidia drivers on hand just in case, assuming it is a bit rich to expect all elements of a bleeding edge development like Compiz to stay in sync in the repositories.

My $0.02.

@ oldcpu I installed my nvidia using nvdia driver sources from the nvidia website , as I dont have a standard config, asfaik oneclick / yast / works as long as you have default kernel.

@watagan, this is what I was also thinking, and I agree.

Exactly the point I would like to make to novell. I dont see why they wont add the issue to bugzilla, albeit its not a major issue and is a easy fix but if official patches are removing symlinks therefore breaking some constellations I fail to see the problem in fixing and reporting the issue , but I guess novell has a different policy. Ive heard of other companies that use the same policy use our drivers use our whatever , but dont ask us to fix or address issues of anything else. Sounds kinda like ms actually.