Xorg crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
X seemingly (seeing as X stayed up running) crashed while logging in with new xorg.conf.
I've needed to fiddle with xorg.conf as 12.10 refuses to run my LCD at its native 1440x900 resolution.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-core 2:1.12.
ProcVersionSign
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.5.1-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Thu Sep 6 12:45:02 2012
DistUpgraded: 2012-08-18 02:53:55,263 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
GraphicsCard:
Advanced Micro Devices [AMD] nee ATI M56P [Radeon Mobility X1600] [1002:71c5] (prog-if 00 [VGA controller])
Subsystem: Apple Inc. MacBook Pro [106b:0080]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: Apple Computer, Inc. MacBookPro1,1
ProcCmdline: /usr/bin/X :0 -core -auth /var/run/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
OsAbort ()
?? ()
FatalError ()
Title: Xorg crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-08-18 (19 days ago)
UserGroups:
dmi.bios.date: 10/12/06
dmi.bios.vendor: Apple Computer, Inc.
dmi.bios.version: MBP11.88Z.
dmi.board.
dmi.board.name: Mac-F425BEC8
dmi.board.vendor: Apple Computer, Inc.
dmi.board.version: PVT
dmi.chassis.
dmi.chassis.type: 8
dmi.chassis.vendor: Apple Computer, Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleCom
dmi.product.name: MacBookPro1,1
dmi.product.
dmi.sys.vendor: Apple Computer, Inc.
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.libdrm2: libdrm2 2.4.38-0ubuntu2
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1037518, 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.