Bug 168686 - X crashes with Nvidia's nvidia driver with Failed to load GLX
X crashes with Nvidia's nvidia driver with Failed to load GLX
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2005-09-19 11:15 EDT by Robert Evans
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-19 18:47:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Evans 2005-09-19 11:15:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.0.6-1.2.fc3 Firefox/1.0.6

Description of problem:
New release xorg-x11-6.8.2-1.FC3.45 crashes on a machine with an NVidia
GeForce2 Mx-400 graphics card when used with NVidia's own Linux driver.

Log shows
(EE) NVIDIA(0): Failed to load GLX
Symbol __glXgetActiveScreen from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved!

Works ok if I use "nv" driver in place of "nvidia". Also works if I comment out
 Load  "glx"
in /etc/X11/xorg.conf.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. upgrade to xorg-x11-6.8.2-1.FC3.45

Actual Results:  X server crashed when restarted

Additional info:

I'm rolling back to xorg-x11-6.8.2-1.FC3.13. We have Intel on-board
graphics on some systems too, and these don't work at all with FC3.45 (there
are other reports of this (see Bug 168623)).
Comment 1 Mike A. Harris 2005-09-19 14:27:20 EDT
If you have installed nvidia's driver downloaded from Nvidia's website, and
installed that, then this problem will happen every time we release an xorg-x11
update.  The reason for this, is that the nvidia installer overwrites xorg-x11
supplied files, such as libglx with their own libglx, and they do not use rpm
packages.  As such, when you upgrade xorg, rpm will overwrite the nvidia files,
because they are in conflict with the rpm managed ones.  The result is that
your nvidia driver will need to be reinstalled again manually.

This is not a bug in our xorg update, but is caused due to not using rpm
to manage nvidia's binary drivers.  Users who wish to avoid this type of
problem, may want to consider using the nvidia rpm packages maintained
by livna.org, which install the driver in a way that does not conflict
with official Red Hat packaging of xorg.  That should ensure files do not
get replaced on upgrades due to being outside of rpm context.

Comment 2 Mike A. Harris 2005-09-19 14:30:02 EDT
Please attach a file with the output of "rpm -V xorg-x11" to the bug
using the file attachment link below.  Also please indicate if you are
using the livna.org rpms or using nvidia's driver direct downloaded
from nvidia and using their custom installer.

Thanks in advance.
Comment 3 Robert Evans 2005-09-19 15:26:36 EDT
You are correct. I used the NVIDIA-Linux-x86-1.0-7667-pkg1.run script to
install the nvidia driver and this, as part of the run, removes libglx*
from the extensions directory. So when the xorg-x11 rpms were updated,
they installed new versions of the libglx libraries which conflict with
NVidia's libglx.so.1.0.7667.

Re-running NVIDIA-Linux-x86-1.0-7667-pkg1.run would fix the problem.
So this isn't bug after all.

Thanks for the hint about the rpms for livna.org. I'll try those
in future.

I've rolled back to release FC3.13 (which didn't work, of course,
because of exactly the same problem with the glx libraries - but I removed
the libraries "by hand" to fix it), so I can't send you any relevant
output.  (I'm keeping FC3.13 until the Intel i810 bug is fixed so that
all my systems are at the same level).
Comment 4 Mike A. Harris 2005-09-19 18:47:02 EDT
Ok, thanks for the update.  Setting bug status to NOTABUG.

Note You need to log in before you can comment on or make changes to this bug.