Ubuntu
xorg-server package

Xorg crashed with SIGSEGV in FatalError() when using guest session

Bug #506510 reported by Vish on 2010-01-12

108

This bug affects 20 people

Affects		Status	Importance	Assigned to	Milestone
	xorg-server (Ubuntu)	Fix Released	High	Unassigned

Bug Description

System frooze when i tried to use a "guest session". Had to hard shutdown. On the next boot i noticed the crash report.

ProblemType: Crash
Architecture: i386
Date: Tue Jan 12 22:06:50 2010
Disassembly: 0x10: Cannot access memory at address 0x10
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
MachineType: Acer, inc. Aspire 5670
Package: xserver-xorg-core 2:1.7.3.902-1ubuntu4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcAttrCurrent: unconfined (enforce)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-10-generic root=UUID=3e905623-5a65-47ef-a1d0-d8fba363d773 ro quiet splash
ProcCmdline: /usr/bin/X :1 -br -verbose -auth /var/run/gdm/auth-for-gdm-rI28XX/database -nolisten tcp vt7
ProcEnviron:
LANG=en_IN
PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
RelatedPackageVersions:
xserver-xorg 1:7.5+1ubuntu1
libgl1-mesa-glx 7.7-0ubuntu4
libdrm2 2.4.17-0ubuntu1
xserver-xorg-video-intel 2:2.9.1-1ubuntu1
xserver-xorg-video-ati 1:6.12.99+git20091125.0061c4db-0ubuntu2
SegvAnalysis:
Segfault happened at: 0x10: Cannot access memory at address 0x10
PC (0x00000010) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
?? ()
FatalError ()
_start ()
Tags: lucid
Title: Xorg crashed with SIGSEGV in FatalError()
Uname: Linux 2.6.32-10-generic i686
UserGroups:

XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 01/12/07
dmi.bios.vendor: Acer
dmi.bios.version: v1.3239
dmi.board.name: Bodensee
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrv1.3239:bd01/12/07:svnAcer,inc.:pnAspire5670:pvrNotApplicable:rvnAcer,Inc.:rnBodensee:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 5670
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.32-10-generic

Tags:

Related branches

lp:ubuntu/lucid/xorg-server

Revision history for this message

Vish (vish) wrote on 2010-01-12:

BootDmesg.txt Edit (53.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.5 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (36.8 KiB, text/plain; charset="utf-8")
GdmLogOld.txt Edit (36.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (27.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (370 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (8.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (717 bytes, text/plain; charset="utf-8")
Registers.txt Edit (451 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (542 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (568 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (101.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (223.9 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (42.7 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (42.7 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.9 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (15.6 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (44.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2010-01-12:

StacktraceTop:
?? ()
FatalError ()
_start ()

Revision history for this message

Apport retracing service (apport) wrote on 2010-01-12: Stacktrace.txt

Stacktrace.txt Edit (542 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2010-01-12: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (569 bytes, text/plain)

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

Vish (vish) on 2010-01-13

visibility:

private → public

Revision history for this message

Bryce Harrington (bryce) wrote on 2010-01-15: Re: Xorg crashed with SIGSEGV in FatalError()

<Sarvatt> this is the commit I was talking about messing with the paths http://git.gnome.org/browse/gdm/commit/?id=e33ee9d9b23c103ac25b6fdb53fe8c074de0de53
doubt hardcoding /sbin/ is the right thing to do, just know it works here

GNU nano 2.2.1 File: /etc/gdm/PreSession/Default

#!/bin/sh
#
# Note that any setup should come before the sessreg command as
# that must be 'exec'ed for the pid to be correct (sessreg uses the parent
# pid)
#
# Note that output goes into the .xsession-errors file for easy debugging
#
PATH="/usr/bin:/sbin:$PATH"

#if [ -x '/usr/bin/xsplash' ];
#then
# /usr/bin/xsplash --daemon
#fi

/sbin/initctl -q emit desktop-session-start DISPLAY_MANAGER=gdm

Revision history for this message

Bryce Harrington (bryce) wrote on 2010-01-15:

<seb128> re
jcristau,
#0 0x080ac9b4 in _XSERVTransClose (ciptr=0x8be8aa8)
     at /usr/include/X11/Xtrans/Xtrans.c:930
#1 0x080a6be4 in CloseWellKnownConnections () at ../../os/connection.c:492
#2 0x080b0caf in SigAbortServer (signo=11) at ../../os/log.c:426
#3 0x080b10d1 in FatalSignal (signo=11) at ../../os/log.c:560
#4 0x080a9aa2 in OsSigHandler (signo=11, sip=0xbfb0f21c, unused=0xbfb0f29c)
     at ../../os/osinit.c:157
#5 <signal handler called>
#6 0x00000000 in ?? ()
#7 0x080b13de in FatalError (f=0x81c5206 "no screens found")
     at ../../os/log.c:585
#8 0x08067044 in main (argc=9, argv=0xbfb0f6c4, envp=0xbfb0f6ec)
     at ../../dix/main.c:206
<seb128> I get it every time I try to open a guest session
but I guess it's nothing specific to the guest session
it's probably when trying to open a second xsession

Bryce Harrington (bryce) on 2010-01-15

summary:

- Xorg crashed with SIGSEGV in FatalError()
+ Xorg crashed with SIGSEGV in FatalError() when using guest session

Revision history for this message

Bryce Harrington (bryce) wrote on 2010-01-15:

This X crash is due to error messages being printed to the log file after the log file has been closed. This was being done in the signal handler due to a Ubuntu patch. I've corrected the patch to not print these errors, which should eliminate this crash.

However, still whatever problem had caused the X error to begin with is still there, and it is likely that X will still be failing, just without crashing (or perhaps with a different kind of crash). This crash is hiding that information however. So the good news is hopefully this will unhide that information. After updating to version 2:1.7.3.902-1ubuntu7 please re-test your original issue; if it still occurs file a new bug. Hopefully apport will provide better information in this case now.

Changed in xorg-server (Ubuntu):
importance:	Medium → High
status:	New → In Progress

Revision history for this message

Launchpad Janitor (janitor) wrote on 2010-01-16:

This bug was fixed in the package xorg-server - 2:1.7.3.902-1ubuntu7

---------------
xorg-server (2:1.7.3.902-1ubuntu7) lucid; urgency=low

  * Update 100_rethrow_signals.patch: Don't log more error messages after
    the log has been closed, else it causes a SIGSEGV (signal 11) crash
    under several different conditions, including on even ordinary error
    exits.
    (LP: #506510, #507345, #506977, #504497, #507083)
-- Bryce Harrington <email address hidden> Fri, 15 Jan 2010 15:22:34 -0800

Changed in xorg-server (Ubuntu):
status:	In Progress → Fix Released

Revision history for this message

Sebastien Bacher (seb128) wrote on 2010-01-18:

The update didn't fix the issue there...

Changed in xorg-server (Ubuntu):
status:	Fix Released → Confirmed

Revision history for this message

Sebastien Bacher (seb128) wrote on 2010-01-18:

#10

the command which crashed is /usr/bin/X :1 -br -verbose -auth /var/run/gdm/auth-for-gdm-wDcN6v/database -nol

(gdb) bt
#0 0x080ac984 in _XSERVTransClose (ciptr=0x8a7caa8)
    at /usr/include/X11/Xtrans/Xtrans.c:930
#1 0x080a6bb4 in CloseWellKnownConnections () at ../../os/connection.c:492
#2 0x080b0c7f in SigAbortServer (signo=11) at ../../os/log.c:402
#3 0x080b10a1 in FatalSignal (signo=11) at ../../os/log.c:536
#4 0x080a9a72 in OsSigHandler (signo=11, sip=0xbfdb0f2c, unused=0xbfdb0fac)
    at ../../os/osinit.c:157
#5 <signal handler called>
#6 0x00000000 in ?? ()
#7 0x080b13ae in FatalError (f=0x81c50a6 <Address 0x81c50a6 out of bounds>)
    at ../../os/log.c:561
#8 0x08067014 in main (argc=9, argv=0xbfdb13d4, envp=0xbfdb13fc)
    at ../../dix/main.c:206

using xorg-server 2:1.7.3.902-1ubuntu8...

Revision history for this message

Sebastien Bacher (seb128) wrote on 2010-01-18:

#11

(the crash happens there when trying to open a guest session on current lucid with an intel 965, the current session gets screwed and the cursor displayed on a vt with text displayed)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2010-01-19:

#12

This bug was fixed in the package xorg-server - 2:1.7.3.902-1ubuntu9

---------------
xorg-server (2:1.7.3.902-1ubuntu9) lucid; urgency=low

  * Fully disable 100_rethrow_signals.patch as it seems to still cause
    crashes. Goodbye apport.
    (LP: #506510)
-- Bryce Harrington <email address hidden> Mon, 18 Jan 2010 23:31:08 -0800

Changed in xorg-server (Ubuntu):
status:	Confirmed → Fix Released

Revision history for this message

Vish (vish) wrote on 2010-01-19:

#13

The crash does happen when trying to switch user too.
If we try to switch user when another user is logged in , the current user session gets screwed and the cursor displayed on a vt with text.

Revision history for this message

Dana Goyette (danagoyette) wrote on 2010-01-19:

#14

Something to consider trying to allow apport to catch Xorg crashes (at the expense of not getting a stacktrace in xorg log): enable NoTrapSignals in xorg.conf.
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-November/006332.html

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #506123

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntuxorg-server package

Xorg crashed with SIGSEGV in FatalError() when using guest session

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xorg-server package