[Paraview] PV 2.0.3 versus Suse Linux 9.3

[SamuelKey]

----- Original Message ----- 
From: "SamuelKey" <samuelkey at comcast.net>
To: <paraview at paraview.org>; <sax at suse.de>
Cc: "Wylie, Brian" <bnwylie at sandia.gov>; <swkey at sandia.gov>
Sent: Sunday, July 10, 2005 2:13 PM
Subject: [Paraview] PV 2.0.3 versus Suse Linux 9.3 Closure

Closure: As suggested by Philip Sackinger, Sandia, I
used xdpyinfo to discover that "GLX" was not currently
an available extension.

I went into Yast (Suse Linux's system management tool)
and discovered that 3D Hardware was disabled for the
graphics card. I enabled 3D hardware and rebooted.
Rerunning xdpyinfo showed that "GLX" was now an
available extension. ParaView runs just fine now.

Sam Key
> There appears to be a naming conflict between
> ParaView (2.0.3) and Xorg's X-window server
> in Suse Linux 9.3
>
> >From a ParaView "failed" startup I get --
> Xlib:  extension "GLX" missing on display ":0.0".
> Aborted
>
> >From the /etc/X11/xorg.conf file I have --
> Section "Module"
>   Load         "dbe"
>   Load         "type1"
>   Load         "freetype"
>   Load         "extmod"
>   Load         "glx"
>   Load         "v4l"
> EndSection
>
> Both files are attached.  My guess at
> what may be the trouble is that ParaView
> is looking for GLX as the extension name,
> and Xorg is using glx as the extension
> name???
>
> Any suggestions on what I should do?


----------------------------------------------------------------------------
----


> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>