Bug 3974 - LSB 4.1: Celestia Test : OpenGL GLX extension not supported by display ':0'
: LSB 4.1: Celestia Test : OpenGL GLX extension not supported by display ':0'
Status: RESOLVED NOTOURBUG
Product: Application Battery
Classification: Unclassified
Component: celestia
: 4.1
: All All
: P2 normal
Assigned To: Jeff Licquia
http://www.xfree86.org/current/DRI8.html
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-01 11:05 UTC by Ashish Yadav
Modified: 2014-05-16 14:15 UTC (History)
1 user (show)

See Also:


Attachments
lspci -v log (5.21 KB, text/x-log)
2014-05-01 16:40 UTC, Ashish Yadav
no flags Details
slow-steady.sh output (107.95 KB, text/plain)
2014-05-02 08:50 UTC, Ashish Yadav
no flags Details
lspci -v Log (5.52 KB, text/plain)
2014-05-02 08:55 UTC, Ashish Yadav
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ashish Yadav 2014-05-01 11:05:15 UTC
While running Celestia Test:
  /opt/lsb/appbat/bin/celestia

I got following error:
   OpenGL GLX extension not supported by display ':0'

I am using x86_64 system (Sandy Bridge).

root@x86-generic-64:~# uname -a
Linux x86-generic-64 3.10.20.x86-generic-64-rt14 #1 SMP PREEMPT Thu Apr 24 19:05:29 IST 2014 x86_64 GNU/Linux


I try to search & debug this issue, but not found any clue.

Is something missing from Display Driver side or its  some lib issue ?

Thanks
Comment 1 Ashish Yadav 2014-05-01 16:40:42 UTC
Created attachment 2409 [details]
lspci -v log
Comment 2 Ashish Yadav 2014-05-02 08:50:31 UTC
Created attachment 2410 [details]
slow-steady.sh output

Hi,

Please find the out for slow-steady.sh, taken from https://raw.githubusercontent.com/herrold/tool-tips/master/broken-system/slow-steady.sh


Please let me know if more info need from my side.

Thanks
Comment 3 Ashish Yadav 2014-05-02 08:55:45 UTC
Created attachment 2411 [details]
lspci -v Log


Please find correct list all PCI devices for my System.
Its Sandy Bridge X86_64 Board.

Thanks
Comment 4 Jeff Licquia 2014-05-02 14:55:53 UTC
What does 'glxinfo' tell you when run in an X session on your machine?
Comment 5 Ashish Yadav 2014-05-05 05:27:41 UTC
(In reply to comment #4)
> What does 'glxinfo' tell you when run in an X session on your machine?

sh-4.2# glxinfo 
glxinfo: error while loading shared libraries: libGLEW.so.1: cannot open shared object file: No such file or directory
sh-4.2# 
sh-4.2#
Comment 6 Ashish Yadav 2014-05-05 07:09:10 UTC
Install glew-1.9.0-r1.x86_64.rpm:

root@x86-generic-64:~# rpm  -ivh glew-1.9.0-r1.x86_64.rpm
Preparing...                ########################################### [100%]
   1:glew                   ########################################### [100%]
/sbin/ldconfig: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf: No such file or directory
/sbin/ldconfig: /lib64/libstdc++.so.6.0.17-gdb.py is not an ELF file - it has the wrong magic bytes at the start.

Now starting startx,
sh-4.2# glxinfo 
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig

sh-4.2#
Comment 7 Jeff Licquia 2014-05-05 19:46:55 UTC
It looks to me like OpenGL support is not working correctly on your distribution.

We don't necessarily require particular kinds of hardware support, but we do require that the OpenGL APIs report the presence or absence of support in a sane manner.  That doesn't look like it's happening with your distribution.

Those errors reported when installing GLEW are also troubling.  I suspect that the problems with working OpenGL support are tied to issues with the dynamic loader being broken, which will have quite a few ripple effects.  So I would start by figuring out what happened to /etc/ld.so.conf, and why the system is trying to load a Python file as if it were the standard C++ library.

A tool which may help you is the Library Check tests in the Distribution Checker.  That should be able to identify any missing or broken shared libraries in your distribution.
Comment 8 R P Herrold 2014-05-05 22:21:23 UTC
As I research this video card, there is some question as to the completeness of its GL conformance

http://www.x.org/archive/X11R6.8.0/doc/siliconmotion.4.html
http://osdir.com/ml/debian-x-debian/2013-03/msg00071.html  
   
As a threshold test, not inside the test suite, as root, is this present and does this run?
   glxgears
run?
Comment 9 Ashish Yadav 2014-05-06 05:50:34 UTC
(In reply to comment #8)
> As I research this video card, there is some question as to the completeness of
> its GL conformance
> 
> http://www.x.org/archive/X11R6.8.0/doc/siliconmotion.4.html
> http://osdir.com/ml/debian-x-debian/2013-03/msg00071.html  
> 
> As a threshold test, not inside the test suite, as root, is this present and
> does this run?
>    glxgears
> run?

While running glxinfo on xterm:
sh-4.2# glxinfo 
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig
sh-4.2#
Comment 10 Ashish Yadav 2014-05-06 07:59:10 UTC
One more thing, while running celestia:

sh-4.2#  /opt/lsb/appbat/bin/celestia 
freeglut (/opt/lsb/appbat/bin/celestia): OpenGL GLX extension not supported by display ':0'
sh-4.2# 



For freegult, if we need to install other packages ? 
 Present package list on machine share in comment#2.
Comment 11 Ashish Yadav 2014-05-07 11:05:16 UTC
(In reply to comment #7)

> 
> A tool which may help you is the Library Check tests in the Distribution
> Checker.  That should be able to identify any missing or broken shared
> libraries in your distribution.

Which tool can help us in identifying any missing or broken shared libraries ?

Also, out from glxgears on xterm shows:

sh-4.2# glxgears
Error: couldn't get an RGB, Double-buffered visual
sh-4.2#
Comment 12 R P Herrold 2014-05-07 17:46:55 UTC
Ashish

This all means that the OpenGL support in the video card driver is the problem.

The x.org folks who wrote your driver need to be contacted.

LSB does not specify a formal need for any specific OpenGL level, but rather expects that when called, that the driver module will do something sensible, rather than segfault

This bug may provide a clean test case for them to look into

Please feel free to reference your bog filing with them in this bug.  UNtil it is updated, we cannot help on this further
Comment 13 Ashish Yadav 2014-05-08 10:10:19 UTC
(In reply to comment #12)
> Ashish
> 
> This all means that the OpenGL support in the video card driver is the problem.
> 
> The x.org folks who wrote your driver need to be contacted.
> 
> LSB does not specify a formal need for any specific OpenGL level, but rather
> expects that when called, that the driver module will do something sensible,
> rather than segfault
> 
> This bug may provide a clean test case for them to look into
> 
> Please feel free to reference your bog filing with them in this bug.  UNtil it
> is updated, we cannot help on this further

Ok Herrold, Thanks for info.
Let me try this test case on Other Hardware setup.
Comment 14 R P Herrold 2014-05-08 20:50:06 UTC
add URL to OpenGL debugging page for the reporter
Comment 15 Ashish Yadav 2014-05-12 05:00:31 UTC
Hi,

After installing some pacakges, like:
libdrm* mesa* libgl* libdricore*  libglapi* xserver-xorg-extension-glx*

Celestia Test Pass.

Thanks
Comment 16 Jeff Licquia 2014-05-16 14:15:21 UTC
Excellent.