python2.6 crashed with SIGSEGV in XF86DRIQueryExtension()

Bug #593272 reported by efa
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: python2.6

typed 'modules' in python shell.
It answer with:
Is there a method to load a python script from the Python shell?
then after a while it core dumped

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: python2.6-minimal 2.6.5-1ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
CheckboxSubmission: 1025977719eeebebe5648c8ca87056aa
CheckboxSystem: 533a8038ef5a55601694b49142442fa7
Date: Sun Jun 13 11:08:55 2010
ExecutablePath: /usr/bin/python2.6
ProcCmdline: python
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=it_IT.utf8
 LANGUAGE=it_IT:it:en_GB:en
SegvAnalysis:
 Segfault happened at: 0x1ca7ef6 <XF86DRIQueryExtension+142>: movzbl 0x4(%esi),%edx
 PC (0x01ca7ef6) ok
 source "0x4(%esi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: python2.6
StacktraceTop:
 XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 ?? ()
 ?? ()
 ?? ()
Title: python2.6 crashed with SIGSEGV in XF86DRIQueryExtension()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare scanner tape video

Revision history for this message
efa (efa) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x01ca7ef6 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 No symbol table info available.
 #1 0x0000000d in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Matthias Klose (doko) wrote :

> typed 'modules' in python shell.

this is caused by some/one module which is imported. I cannot reproduce it here myself. you need to find out which module causes the crash

Changed in python2.6 (Ubuntu):
status: New → Incomplete
visibility: private → public
Matthias Klose (doko)
affects: python2.6 (Ubuntu) → fglrx-installer (Ubuntu)
Revision history for this message
Felix Kuehling (felix-kuehling) wrote :

This usually happens when the wrong libGL is in use. Either fglrx is installed but a stale libGL is in /usr/lib, or fglrx is installed but not actually in use (not configured in xorg.conf).

To know what's going on I'd like to see Xorg.0.log and xorg.conf from an affected system as well as the output of

ls -l /usr/lib/ligGL*
ls -l /usr/lib/fglrx

Revision history for this message
Bryce Harrington (bryce) wrote :

[Resetting to incomplete since we need a response from the original reporter on this].

Changed in fglrx-installer (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
efa (efa) wrote :

Here the fist part of answer:

efa@01ath3200:~$ ls -l /usr/lib/ligGL*
ls: impossibile accedere a /usr/lib/ligGL*: Nessun file o directory
efa@01ath3200:~$ ls -l /usr/lib/fglrx
totale 0
lrwxrwxrwx 1 root root 15 2010-05-04 08:39 libXvBAW.so.1 -> libXvBAW.so.1.0

BTW: I removed fglrx some time after June, as it crash Wine applications.

Revision history for this message
efa (efa) wrote :

efa@01ath3200:~$ cat /etc/X11/xorg.conf

Section "Screen"
 Identifier "Configured Screen Device"
 Device "Configured Video Device"
 SubSection "Display"
  Virtual 2304 1024
 EndSubSection
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

Revision history for this message
efa (efa) wrote :
Revision history for this message
efa (efa) wrote :

I retest the help "modules" command in python shell, and now work. So seems related to fglrx

Revision history for this message
Felix Kuehling (felix-kuehling) wrote :

Sorry, I had a typo in my request. I need the output of

ls -l /usr/lib/libGL*

Either way, if you uninstalled fglrx, the problem is gone and no one else has this problem, I guess this bug report can be closed.

Revision history for this message
efa (efa) wrote :

efa@01ath3200:~$ ls -l /usr/lib/libGL*
lrwxrwxrwx 1 root root 16 2010-05-04 01:33 /usr/lib/libGLEW.so.1.5 -> libGLEW.so.1.5.2
-rw-r--r-- 1 root root 300360 2010-01-17 08:07 /usr/lib/libGLEW.so.1.5.2
lrwxrwxrwx 1 root root 13 2010-05-14 22:24 /usr/lib/libGL.so -> mesa/libGL.so
-rw-r--r-- 1 root root 716290 2010-04-29 07:43 /usr/lib/libGLU.a
lrwxrwxrwx 1 root root 11 2010-05-14 22:24 /usr/lib/libGLU.so -> libGLU.so.1
lrwxrwxrwx 1 root root 20 2010-05-14 22:24 /usr/lib/libGLU.so.1 -> libGLU.so.1.3.070701
-rw-r--r-- 1 root root 456380 2010-04-29 07:43 /usr/lib/libGLU.so.1.3.070701

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for fglrx-installer (Ubuntu) because there has been no activity for 60 days.]

Changed in fglrx-installer (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.