[i945gm] panda3d segmentation fault (intel driver)

Bug #378106 reported by Yuioup
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Fix Released

Bug Description

Binary package hint: xserver-xorg-video-intel

Running any panda3d sample causes a segmentation fault.

This is the output:

DirectStart: Starting the game.
Known pipe types:
(all display modules loaded.)
get fences failed: -1
param: 6, val: 0
Segmentation fault

The "get fences failed" message get thrown every time an opengl app is started (like glxgears).

On the panda3d forums a poster suspects that it has to do with the intel drivers:


I'm running jaunty on an asus eee pc 1000HE


Description: Ubuntu 9.04
Release: 9.04

  Installed: 2:2.6.3-0ubuntu9
  Candidate: 2:2.6.3-0ubuntu9
  Version table:
 *** 2:2.6.3-0ubuntu9 0
        500 http://nl.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03)
 Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03)
 Subsystem: ASUSTeK Computer Inc. Device [1043:8340]

Yuioup (mghaoui)
summary: - panda3d segmentation fault due to faulty intel driver
+ panda3d segmentation fault (intel driver)
description: updated
Revision history for this message
Geir Ove Myhr (gomyhr) wrote : Re: panda3d segmentation fault (intel driver)

Thank you for taking the time to report this bug. For Xorg related bugs, there is some information we always need:
- /var/log/Xorg.0.log
- the output of `lspci -vvnn`

Moreover, since this is a crash (segmentation fault), we would need a backtrace to find out why it crashes. You may take a look at
https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport for how to enable apport and get a backtrace. You may also do it without apport, look at https://wiki.ubuntu.com/Backtrace .

Geir Ove Myhr (gomyhr)
Changed in xserver-xorg-video-intel (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Yuioup (mghaoui) wrote :

Here is my Xorg.0.log

Revision history for this message
Yuioup (mghaoui) wrote :

The output of `lspci -vvnn`

Revision history for this message
Yuioup (mghaoui) wrote :

I've submitted the backtrace information. You can find it here:


Bug #384203

Geir Ove Myhr (gomyhr)
description: updated
tags: added: 945gme crash xorg
summary: - panda3d segmentation fault (intel driver)
+ [i945gm] panda3d segmentation fault (intel driver)
Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

It seems the apport backtrace didn't work very well in this case. There is almost no useful information at bug 384203. Are you MojoX in that forum thread? There is a useful backtrace there, but it could have more information. First of all, there are some debug symbols missing (?? in the backtrace). They would probably show up if the right -dbg packages were installed. Look at https://wiki.ubuntu.com/X/Backtracing#Debug%20symbol%20information for packages that may have the necessary debug symbols. Also a full backtrace is better: Instead of `bt` in gdb, write `bt full`.

You may also wish to check if this has been fixed in karmic, by using a daily Live-CD from http://cdimage.ubuntu.com/daily-live/ or alpha-2 which will soon be available at http://cdimage.ubuntu.com/releases/9.10/ .

Revision history for this message
Yuioup (mghaoui) wrote :

I downloaded karmic alpha-2 netbook remix and have tested the apps. I don't get a segmentation fault and the pands3d apps launch fine.

So it looks like it has been fixed ;-)

Thanks for looking into this.


(I am typing this post on karmic alpha-2 netbook remix)

Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

Thank you for letting us know that this has been fixed in Karmic. Closing this bug.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers