Ubuntu
virtualbox-ose package

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

Bug #362196 reported by Patryk Bajer on 2009-04-16

This bug report is a duplicate of: Bug #362127: Xorg crashed with SIGSEGV in DamageUnregister(). Edit Remove

120

This bug affects 28 people

Affects		Status	Importance	Assigned to	Milestone
	virtualbox-ose (Ubuntu)	New	Medium	Unassigned

Bug Description

After booting and logging in. Using VirtualBox 2.2 with Compiz turned on. Clean system with the latest updates.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/Xorg
Package: xserver-xorg-core 2:1.6.0-0ubuntu14
ProcAttrCurrent: unconfined
ProcCmdline: /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
?? ()
<signal handler called>
select () from /lib/libc.so.6
WaitForSomething ()
Dispatch ()
Title: Xorg crashed with SIGSEGV in <signal handler called>()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02)
00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef]
Subsystem: Intel Corporation Device [8086:001e]

See original description

Tags:

Revision history for this message

Patryk Bajer (bayger) wrote on 2009-04-16:

Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (511 bytes, text/plain; charset="utf-8")
LsHal.txt Edit (71.9 KiB, text/plain; charset="utf-8")
LsMod.txt Edit (2.0 KiB, text/plain; charset="utf-8")
LsPci.txt Edit (5.0 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (20.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (721 bytes, text/plain; charset="utf-8")
Registers.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (535 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (562 bytes, text/plain; charset="utf-8")
XorgConf.txt Edit (1.0 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (16.1 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (16.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (1.2 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (11.5 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (234 bytes, text/plain; charset="utf-8")
system.txt Edit (279 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (46.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-04-17: Stacktrace.txt (retraced)

Stacktrace.txt (retraced) Edit (2.0 KiB, text/plain)

StacktraceTop:?? ()
<signal handler called>
__select_nocancel () from /lib/libc.so.6
WaitForSomething (pClientsReady=0xf49a80)
Dispatch () at ../../dix/dispatch.c:367

Revision history for this message

Apport retracing service (apport) wrote on 2009-04-17: ThreadStacktrace.txt (retraced)

ThreadStacktrace.txt (retraced) Edit (2.1 KiB, text/plain)

Changed in xorg-server (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Bryce Harrington (bryce) on 2009-04-20

tags:	added: crash
Changed in xorg-server (Ubuntu):
status:	New → Confirmed

Bryce Harrington (bryce) on 2009-04-21

description:

updated

Revision history for this message

Bryce Harrington (bryce) wrote on 2009-05-09:

Thanks for reporting this issue. VirtualBox provides its own X driver, and this seems to be an issue with that. Reassigning

affects:	xorg-server (Ubuntu) → virtualbox-ose (Ubuntu)
Changed in virtualbox-ose (Ubuntu):
status:	Confirmed → New

Connor Imes (ckimes) on 2009-05-24

visibility:

private → public

Revision history for this message

Scott Lewin (sclewin) wrote on 2009-08-04:

This problems seems to persist in Ubuntu 9.10. I have received the same problem, also using VirtualBox, but with Ubuntu 9.10 Alpha 3.

Revision history for this message

cohnuh69 (tom-cohnen) wrote on 2009-08-04: Re: [Bug 362196] Re: Xorg crashed with SIGSEGV in <signal handler called>()

I have used ubuntu 9.10 alpha 3 on a notebook when it happend

2009/8/4 Scott Lewin <email address hidden>

> This problems seems to persist in Ubuntu 9.10. I have received the same
> problem, also using VirtualBox, but with Ubuntu 9.10 Alpha 3.
>
> --
> Xorg crashed with SIGSEGV in <signal handler called>()
> https://bugs.launchpad.net/bugs/362196
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “virtualbox-ose” package in Ubuntu: New
>
> Bug description:
> After booting and logging in. Using VirtualBox 2.2 with Compiz turned on.
> Clean system with the latest updates.
>
> ProblemType: Crash
> Architecture: amd64
> CrashCounter: 1
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/bin/Xorg
> Package: xserver-xorg-core 2:1.6.0-0ubuntu14
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth
> -nolisten tcp vt7
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version
> 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009
> Signal: 11
> SourcePackage: xorg-server
> StacktraceTop:
> ?? ()
> <signal handler called>
> select () from /lib/libc.so.6
> WaitForSomething ()
> Dispatch ()
> Title: Xorg crashed with SIGSEGV in <signal handler called>()
> Uname: Linux 2.6.28-11-generic x86_64
> UserGroups:
>
> [lspci]
> 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma]
> [8086:1237] (rev 02)
> 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH
> VirtualBox Graphics Adapter [80ee:beef]
> Subsystem: Intel Corporation Device [8086:001e]
>
>

Revision history for this message

Copernicus (twowayspirit) wrote on 2009-08-24:

Happened in Karmic Koala last alpha version, but yes, Im running in VirtualBox so it could be their drivers.

Revision history for this message

Jonathan M. Prigot (jprigot) wrote on 2009-08-25:

I got this while running VirtualBox 3.0.4 on 9.10 Alpha-4.

Revision history for this message

Dirschl Andreas (dirschl-andreas) wrote on 2009-08-28:

Same here. Virtual Box 2.1.4, 9.10 Alpha-4

Revision history for this message

Felix Geyer (debfx) wrote on 2009-09-03:

#10

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

Revision history for this message

Jacob Taylor (orangewinds) wrote on 2009-09-03:

#11

When it "Crashed" for me, it ( as far as I could tell) never actually crashed. Unless it was before I got to the login screen or something, it never visibly crashed. I'm not sure what crashing xorg would look like, but it definetely didn't look out of character at all when the thing popped up saying something (xorg) had crashed.