Ubuntu
xorg-server package

Xorg crashed with SIGSEGV in <signal handler called>()

Bug #472028 reported by Diego Nartallo on 2009-11-03

This bug report is a duplicate of: Bug #357536: Xorg crashed with SIGSEGV in miPointerGetScreen() via CloseDownDevices(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xorg-server (Ubuntu)	New	Undecided	Unassigned

Bug Description

It happens only one time. I log out and log in then appears the option to report this bug.

ProblemType: Crash
Architecture: amd64
Date: Mon Nov 2 22:13:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
MachineType: Hewlett-Packard HP 550
NonfreeKernelModules: wl
Package: xserver-xorg-core 2:1.6.4-2ubuntu4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=b38ead58-9405-4482-ac6f-32882d5ecae1 ro quiet splash
ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-kRISgA/database -nolisten tcp vt7
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
xserver-xorg 1:7.4+3ubuntu7
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-xorg-video-intel 2:2.9.0-1ubuntu2
xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SegvAnalysis:
Segfault happened at: 0x434a9a <dixLookupPrivate+10>: mov (%rdi),%rdx
PC (0x00434a9a) ok
source "(%rdi)" (0x00000198) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
?? ()
<signal handler called>
sigprocmask () from /lib/libc.so.6
CloseDownDevices ()
main ()
Title: Xorg crashed with SIGSEGV in <signal handler called>()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

dmi.bios.date: 06/20/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MVU Ver. F.01
dmi.board.name: 3618
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 12.00
dmi.chassis.asset.tag: CNU83335LX
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVUVer.F.01:bd06/20/2008:svnHewlett-Packard:pnHP550:pvrF.01:rvnHewlett-Packard:rn3618:rvrKBCVersion12.00:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP 550
dmi.product.version: F.01
dmi.sys.vendor: Hewlett-Packard
fglrx: Not loaded
system:
distro: Ubuntu
architecture: x86_64kernel: 2.6.31-14-generic

Tags:

Revision history for this message

Diego Nartallo (dnartallo) wrote on 2009-11-03:

BootDmesg.txt Edit (47.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (6.9 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (144.7 KiB, text/plain; charset="utf-8")
GdmLogOld.txt Edit (903.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (19.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (514 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.8 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (102.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (205.5 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.1 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (148.1 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (907.7 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (8.8 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (16.6 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (303 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (19.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (56.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-06: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #357536, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.