Xorg crashed with SIGABRT in OsAbort()

[Aneesh Neelam]

I installed Mir and restarted lightdm service.

Then it went into low graphics mode. I switched to a VT and rebooted.
Then it booted fine, but graphics was slightly slower.

unity-system-compositor is present in the list of processes, which indicates Mir is running fine.

My laptop is the Dell XPS 502X, it has the Intel HD 3000 as well as Nvidia Geforce 540M.
But I disabled the Nvidia Card using bbswitch.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-core 2:1.14.2.901-2ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.12-0ubuntu3
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
Date: Fri Aug 16 21:28:58 2013
DistUpgraded: 2013-07-04 18:08:38,192 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:050e]
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff)
InstallationDate: Installed on 2013-01-22 (206 days ago)
InstallationMedia: This
MachineType: Dell Inc. Dell System XPS L502X
MarkForUpload: True
ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -mir 0 -mirSocket /tmp/mir_socket -nolisten tcp
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-2-generic root=UUID=a20fb25c-73db-4bfd-94c4-84ae76bb34ae ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 ?? ()
 __libc_start_main (main=0x7f4b29896160, argc=11, ubp_av=0x7fff799c2d28, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff799c2d18) at libc-start.c:260
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: Upgraded to saucy on 2013-07-04 (43 days ago)
UserGroups:

dmi.bios.date: 09/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0NJT03
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L502X
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.6-2ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.1.6-2ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.6-2ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu1
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-0ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
xserver.bootTime: Fri Aug 16 21:30:27 2013
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.14.2.901-2ubuntu1

[Aneesh Neelam (aneesh-neelam)]

unity-system-compositor is present, Mir is present and enabled.

Although it seems slightly slower than before.

[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.