Xorg crashed with SIGSEGV in shadowRemove()

Bug #417014 reported by iolar
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virtualbox-ose (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

X crashes on startup of Karmic Alpha 4 running as a VM client under VirtualBox 3.0.4 (latest version). Then reverts to max 800x600 screen resolution. Regression: previously worked under Jaunty & in Karmic Alpha 3

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Aug 17 11:34:12 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: xserver-xorg-core 2:1.6.3-1ubuntu3
PciDisplay:
 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef]
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
  Latency: 0
  Region 0: Memory at e0000000 (32-bit, prefetchable) [size=16M]
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-6-generic root=UUID=65f7ea63-f867-411e-860a-46c7e382ab31 ro quiet splash
ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-47G871/database -nolisten tcp vt7
ProcEnviron:
 LANG=en_IE.UTF-8
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.5-1ubuntu1
 libdrm2 2.4.12-1ubuntu1
 xserver-xorg-video-intel 2:2.8.0-0ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu6
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? ()
 shadowRemove () from /usr/lib/xorg/modules//libshadow.so
 ?? () from /usr/lib/xorg/modules//libshadow.so
 ?? ()
 ?? ()
Title: Xorg crashed with SIGSEGV in shadowRemove()
Uname: Linux 2.6.31-6-generic i686
UserGroups:

dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-6-generic
SegvAnalysis:
 Segfault happened at: 0x817e1fa: mov %edi,-0x4(%ebp)
 PC (0x0817e1fa) ok
 source "%edi" ok
 destination "-0x4(%ebp)" (0xbfbdcee4) ok
 SP (0xbfbdcec0) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

Revision history for this message
iolar (iolar) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:damageValidateGC (pGC=0x9b07ab0, changes=162372560,
shadowRemove (pScreen=0x9adb118, pPixmap=0x9b07ab0)
shadowCloseScreen (i=0, pScreen=0x9adb118)
DGAHandleEvent (screen_num=0, event=0x9adb118,
miDCDeviceCleanup (pDev=0x0, pScreen=0x9adb118)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Bryce Harrington (bryce)
tags: added: crash
Changed in xorg-server (Ubuntu):
status: New → Confirmed
iolar (iolar)
visibility: private → public
Bryce Harrington (bryce)
tags: added: karmic
Bryce Harrington (bryce)
affects: xorg-server (Ubuntu) → virtualbox-ose (Ubuntu)
Revision history for this message
Felix Geyer (debfx) wrote :

Does the X server actually crash or is the apport dialog just popping up?

Kees Cook (kees)
description: updated
Felix Geyer (debfx)
Changed in virtualbox-ose (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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