MojoX
April 27, 2009, 7:49pm
1
Whenever I attempt to run an app, including the samples, I see the window open and can se the scene for a couple of seconds and then I get the following error:
I am running Ubuntu Jaunty. I am am on a laptop with an Intel graphics chip (940GM). I also had the same error running 1.6.0. Any help or direction in fixing this will be appreciated. Thanks.
Xidram
April 28, 2009, 2:00am
2
This is probably not of much use, and I am sorry for that, but I felt the need to say that I do not get the same error with 1.6.1 on Ubuntu Jaunty 64-bit; desktop with Nvidia graphics card (G8800GT). Everything seems to work fine on here. Perhaps someone more knowledgeable can diagnose MojoX’s problem?
MojoX
April 28, 2009, 2:10am
3
Xidram:
This is probably not of much use, and I am sorry for that, but I felt the need to say that I do not get the same error with 1.6.1 on Ubuntu Jaunty 64-bit; desktop with Nvidia graphics card (G8800GT). Everything seems to work fine on here. Perhaps someone more knowledgeable can diagnose MojoX’s problem?
No, problem. I’m guessing it has something to do with my system. What I would like to know is what the “get fences failed” message might mean.
rdb
April 28, 2009, 5:52am
4
Can you run pview?
Also, can you give us a gdb traceback so we’ll know where to look?
MojoX
April 28, 2009, 4:06pm
5
No, I cannot run pview.
Here is the gdb traceback:
Starting program: /usr/bin/python “Tut-Roaming-Ralph.py”
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
DirectStart: Starting the game.
[New Thread 0xb7e456c0 (LWP 889)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
—Type to continue, or q to quit—
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Known pipe types:
glxGraphicsPipe
(all display modules loaded.)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
get fences failed: -1
param: 6, val: 0
—Type to continue, or q to quit—
(no debugging symbols found)
(no debugging symbols found)
:audio(error): _system->init(): Error initializing output device.
:audio(error): FmodAudioManager is not valid, will use NullAudioManager
:audio(error): _system->init(): Error initializing output device.
:audio(error): FmodAudioManager is not valid, will use NullAudioManager
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7e456c0 (LWP 889)]
0xb3efe960 in ?? () from /usr/lib/dri/i915_dri.so
(gdb)
(gdb) bt
#0 0xb3efe960 in ?? () from /usr/lib/dri/i915_dri.so
#1 0xb3e7a884 in _tnl_run_pipeline () from /usr/lib/dri/i915_dri.so
#2 0xb3dcd6b9 in ?? () from /usr/lib/dri/i915_dri.so
#3 0xb3e7adf5 in _tnl_draw_prims () from /usr/lib/dri/i915_dri.so
#4 0xb3e73420 in ?? () from /usr/lib/dri/i915_dri.so
#5 0xb3d99425 in intel_clear_tris () from /usr/lib/dri/i915_dri.so
#6 0xb3d998de in ?? () from /usr/lib/dri/i915_dri.so
#7 0xb3deb7a9 in _mesa_Clear () from /usr/lib/dri/i915_dri.so
#8 0xb437e276 in GLGraphicsStateGuardian::clear ()
from /usr/lib/panda3d/libpandagl.so
#9 0xb5986782 in GraphicsOutput::clear () from /usr/lib/panda3d/libpanda.so
#10 0xb59a12fa in GraphicsEngine::draw_bins ()
from /usr/lib/panda3d/libpanda.so
#11 0xb59a9ba2 in GraphicsEngine::WindowRenderer::do_frame ()
from /usr/lib/panda3d/libpanda.so
#12 0xb59aa779 in GraphicsEngine::render_frame ()
from /usr/lib/panda3d/libpanda.so
#13 0xb59dff1b in ?? () from /usr/lib/panda3d/libpanda.so
#14 0x080de562 in PyEval_EvalFrameEx ()
#15 0x080e00b8 in PyEval_EvalCodeEx ()
#16 0x081687df in ?? ()
#17 0x0806111a in PyObject_Call ()
#18 0x0806801a in ?? ()
#19 0x0806111a in PyObject_Call ()
#20 0xb5a1696a in Thread::call_python_func () from /usr/lib/panda3d/libpanda.so
#21 0xb5a2e197 in PythonTask::do_python_task ()
from /usr/lib/panda3d/libpanda.so
#22 0xb5a2e47d in PythonTask::do_task () from /usr/lib/panda3d/libpanda.so
#23 0xb5a356d2 in AsyncTask::unlock_and_do_task ()
from /usr/lib/panda3d/libpanda.so
#24 0xb5a3e6c1 in AsyncTaskChain::service_one_task ()
from /usr/lib/panda3d/libpanda.so
#25 0xb5a3f90a in AsyncTaskChain::do_poll () from /usr/lib/panda3d/libpanda.so
#26 0xb5a3fa4b in AsyncTaskManager::poll () from /usr/lib/panda3d/libpanda.so
#27 0xb5a5425b in ?? () from /usr/lib/panda3d/libpanda.so
#28 0x080de562 in PyEval_EvalFrameEx ()
#29 0x080df587 in PyEval_EvalFrameEx ()
#30 0x080e00b8 in PyEval_EvalCodeEx ()
#31 0x080de5f8 in PyEval_EvalFrameEx ()
#32 0x080df587 in PyEval_EvalFrameEx ()
#33 0x080e00b8 in PyEval_EvalCodeEx ()
#34 0x080e0217 in PyEval_EvalCode ()
#35 0x080fe0e1 in PyRun_FileExFlags ()
#36 0x080fe43a in PyRun_SimpleFileExFlags ()
#37 0x0805c882 in Py_Main ()
#38 0x0805b972 in main ()
drwr
April 28, 2009, 6:10pm
6
It appears to be crashing deep within your OpenGL driver. I suspect a driver misconfiguration. Are you able to run any other 3-D applications?
David
MojoX
April 30, 2009, 5:00am
7
Thanks for the help. The problem does seem to be with the driver. Apparently quite a few folks who upgraded to Ubuntu 9.4 are having problems with the Intel drivers. Hopefully, the problem will be resolved soon. Again, thanks.
I appear to be having the same issue.
Dell D410
Intel 915gm onboard video
GLgears works fine
Compiz Fusion working perfectly
i’ve googled the issue but have not found a solution.
have also gone to ubuntuforums.org and searched there, no solution
drwr
August 3, 2009, 11:27pm
9
Does it run if you set:
load-display tinydisplay
in your Config.prc, replacing the “pandagl” line? This will configure Panda to use its own software renderer instead of your system drivers. If this works, it does prove that something’s not quite right in the communication between your drivers and Panda.
David
load-display tinydisplay
#load-display pandagl
#load-display pandadx9
#load-display pandadx8
received the following error:
:display(warning): Unable to load: /usr/lib/panda3d/libtinydisplay.so: undefined symbol: XAllocSizeHints
Known pipe types:
(all display modules loaded.)
No graphics pipe is available!
Your Config.prc file must name at least one valid panda display
library via load-display or aux-display.
I had the same problem: ubuntu jaunty and intel video card. It seems this problem was addressed already in the next ubuntu release:
bugs.launchpad.net/ubuntu/+sour … bug/378106
So the solution is to upgrade to ubuntu karmic.