Xorg crashed with SIGABRT in OsAbort()

[jerrylamos]

Saucy Beta 2 3.11.0-11 booted up shortly thereafter got this internal error. Has happened on every boot today. apt-get update & dist-upgrade ran earlier today.

Acer Aspire 1 D255E Intel Atom N455
Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-core 2:1.14.3-3ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Fri Oct 4 14:37:24 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
InstallationDate: Installed on 2013-09-28 (6 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MachineType: Acer AOD255E
MarkForUpload: True
ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=cc14937c-d48f-48fa-8777-b50adfef3800 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 ?? ()
 __libc_start_main (main=0x7f35a96cb1a0, argc=9, ubp_av=0x7fffdd033ee8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffdd033ed8) at libc-start.c:260
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/16/2010
dmi.bios.vendor: Acer
dmi.bios.version: V3.12(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE02_PT
dmi.board.vendor: Acer
dmi.board.version: V3.12(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V3.12(DDR3)
dmi.modalias: dmi:bvnAcer:bvrV3.12(DDR3):bd12/16/2010:svnAcer:pnAOD255E:pvrV3.12(DDR3):rvnAcer:rnJE02_PT:rvrV3.12(DDR3):cvnAcer:ct10:cvrV3.12(DDR3):
dmi.product.name: AOD255E
dmi.product.version: V3.12(DDR3)
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Fri Oct 4 17:09:16 2013
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 12838
 vendor COB
xserver.version: 2:1.14.3-3ubuntu1

[Chris Wilson (ickle)]

Afaict those logs do not correspond with the stacktrace - there's no sign a crash there. The stacktrace that has been captured is incomplete, but looks to be coming from the core xserver. I wonder if the retracing service will enlighten us?

[Apport retracing service (apport)]

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 #1188123, 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.