Xorg crashed with SIGSEGV in _Unwind_IteratePhdrCallback()

Bug #969087 reported by duolon
72
This bug affects 10 people
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This bug appears today after i update my system.
and, my laptop seems to be overheat, is it related to this bug too?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CrashCounter: 1
Date: Fri Mar 30 18:58:05 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus: fglrx, 8.960, 3.2.0-20-generic, x86_64: installed
ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120321)
MachineType: ASUSTeK Computer Inc. K52Dr
ProcCmdline: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=84209d30-b08c-494d-a26f-edf13c755f83 ro quiet splash vt.handoff=7
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: fglrx-installer
Title: Xorg crashed with SIGSEGV in dl_iterate_phdr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/18/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52Dr.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K52Dr
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK52Dr.211:bd08/18/2010:svnASUSTeKComputerInc.:pnK52Dr:pvr1.0:rvnASUSTeKComputerInc.:rnK52Dr:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K52Dr
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.7.2-0ubuntu4
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

Revision history for this message
duolon (lssscut) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in fglrx-installer (Ubuntu):
importance: Undecided → Medium
summary: - Xorg crashed with SIGSEGV in dl_iterate_phdr()
+ Xorg crashed with SIGSEGV in _Unwind_IteratePhdrCallback()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
Revision history for this message
Boyan Sotirov (lz1dsb) wrote :

It seems like I'm affected by this bug too. I'm using Dell Studio 1555 with an ATI Radeon Mobility video card. The fglrx driver is installed. What shall I do in order to collect more information about this crash? It seems that this issue is quite an old one... Is there any development?

To post a comment you must log in.