Xorg crashed with SIGSEGV in FatalError() / CloseWellKnownConnections()

Bug #507345 reported by Nicholas Christian Langkjær Ipsen
80
This bug affects 16 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
High
Unassigned

Bug Description

The system boots up fairly normally(Plymouth is a no-show for now), but this then shows up on its own. I should add that it works perfectly fine, apart from running in low-graphics mode.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Jan 14 07:04:05 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
MachineType: GIGABYTE M1028
Package: xserver-xorg-core 2:1.7.3.902-1ubuntu5
ProcAttrCurrent: unconfined (enforce)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-10-generic root=UUID=33f45800-d1dc-45aa-9098-839ef5477cac ro quiet splash i8042.noloop=1
ProcCmdline: /usr/bin/X :1 -br -verbose -auth /var/run/gdm/auth-for-gdm-ckE2KE/database -nolisten tcp
ProcEnviron:
 LANG=en_DK.UTF-8
 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: 0x80ac9b4: call *0x44(%eax)
 PC (0x080ac9b4) ok
 source "*0x44(%eax)" ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? ()
 FatalError ()
 _start ()
Tags: ubuntu-unr 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: 07/17/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: T1028 FB
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: M1028E
dmi.board.vendor: Gigabyte Technology Co.,Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Insyde
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrT1028FB:bd07/17/2009:svnGIGABYTE:pnM1028:pvr1:rvnGigabyteTechnologyCo.,Ltd.:rnM1028E:rvr2.0:cvnInsyde:ct1:cvrChassisVersion:
dmi.product.name: M1028
dmi.product.version: 1
dmi.sys.vendor: GIGABYTE
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.32-10-generic

Related branches

Revision history for this message
Nicholas Christian Langkjær Ipsen (ncli) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
description: updated
Bryce Harrington (bryce)
visibility: private → public
Bryce Harrington (bryce)
summary: - Xorg crashed with SIGSEGV in FatalError()
+ Xorg crashed with SIGSEGV in FatalError() / CloseWellKnownConnections()
Revision history for this message
Bryce Harrington (bryce) wrote :

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 :

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
ghostdog (chiggavelli) wrote :

i dont see its fixed im getting low graphic interface cant install normal ati drivers, im using msi radeon R4350, after i pushed ctrl+alt+f1 all started everything befoure was fine.

X Error of failed request: BadRequest (invalid request code or no such operation)
  Major opcode of failed request: 135 (GLX)
  Minor opcode of failed request: 19 (X_GLXQueryServerString)
  Serial number of failed request: 16
  Current serial number in output stream: 16

Revision history for this message
ghostdog (chiggavelli) wrote :

There was a problem initializing Catalyst Control Center Linux edition. It could be caused by the following.

No ATI graphics driver is installed, or the ATI driver is not functioning properly.
Please install the ATI driver appropriate for you ATI hardware, or configure using aticonfig.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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