Xorg crashed with SIGABRT in OsAbort()

[Chris Halse Rogers]

This is a somewhat flaky hybrid system (the hardware is fine, but the Ubuntu hybrid detection & setup fails and I need to manually write an xorg.conf)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-core 2:1.19.3-1ubuntu2
ProcVersionSignature: Ubuntu 4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic 4.11.3
Uname: Linux 4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CrashCounter: 1
Date: Thu Aug 3 19:42:05 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed
 bbswitch, 0.8, 4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic, x86_64: installed
 nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed
 nvidia-384, 384.59, 4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic, x86_64: installed
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
 NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev ff) (prog-if ff)
MachineType: System76 Oryx Pro
ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/125/gdm/Xauthority -background none -noreset -keeptty -verbose 7 -core
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic root=UUID=912b1771-d5ce-4e19-955b-f60f617ef8ad ro fbcon=map:1 splash quiet vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 ?? ()
 __libc_start_main (main=0x560084436590, argc=13, argv=0x7fff80e5f948, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7fff80e5f938) at ../csu/libc-start.c:291
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/20/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.02dRSA1 02/20/2017
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76
dmi.board.version: oryp3-ess
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
dmi.product.name: Oryx Pro
dmi.product.version: oryp3-ess
dmi.sys.vendor: System76
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Aug 3 19:45:20 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 modeset(G0): eglGetDisplay() failed
 modeset(G0): glamor initialization failed
 systemd-logind: failed to release device: Device not taken
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu2

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