Xorg crashed with SIGABRT in OsAbort()

[Frederick Billings]

This bug happened after logging in, upon loading Wily

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: xserver-xorg-core 2:1.17.2-1ubuntu7
ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1
Uname: Linux 4.2.0-11-lowlatency x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Sep 27 02:17:05 2015
DistUpgraded: 2015-09-26 23:09:29,841 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
InstallationDate: Installed on 2015-09-06 (20 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1235:8012 Focusrite-Novation Scarlett 6i6
 Bus 001 Device 002: ID 03f0:1604 Hewlett-Packard DeskJet 940c
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/bin/X vt7 -displayfd 3 -auth /run/user/121/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-lowlatency root=UUID=96c5437a-eb6d-4edc-ade7-e17bdc6d57e4 ro splash crashkernel=384M-:128M vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 FatalError ()
 ?? ()
 xf86CloseConsole ()
 ddxGiveUp ()
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: Upgraded to wily on 2015-09-27 (0 days ago)
UserGroups:

dmi.bios.date: 08/13/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: Default string
dmi.board.name: Z170-P D3
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd08/13/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.65+git1509220630.f3c674~gd~v
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1~git1509261930.511a86~gd~v
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1~git1509261930.511a86~gd~v
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.99+git1508200731.0288a4~gd~v
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1509231931.f0fd4d~gd~v
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git1509140732.1ff13a~gd~v
xserver.bootTime: Sun Sep 27 02:17:51 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 5047
 vendor LEN
xserver.version: 2:1.17.2-1ubuntu7

[Frederick Billings (phonesyfreakies)]

Note that I am subscribed to the oiabf intel graphics PPA, which may have replaced some xorg packages with different/incompatible versions, therefore I am not totally sure whether this bug report is even appropriate. I'm new to launchpad.

[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 #1237904, 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.