desktop-packages team mailing list archive
Mailing list archive
[Bug 1544252] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1543192 ***
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
** Attachment removed: "CoreDump.gz"
** Attachment removed: "Disassembly.txt"
** Attachment removed: "ProcMaps.txt"
** Attachment removed: "ProcStatus.txt"
** Attachment removed: "Registers.txt"
** Attachment removed: "Stacktrace.txt"
** Attachment removed: "ThreadStacktrace.txt"
** This bug has been marked a duplicate of private bug 1543192
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Xorg crashed with SIGABRT in OsAbort()
Status in xorg-server package in Ubuntu:
upgraded from chromeos to a galliumos kernel, then dist-upgrade to
stock ubuntu kernel
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
Date: Wed Feb 10 14:31:34 2016
InstallationDate: Installed on 2016-02-09 (1 days ago)
InstallationMedia: GalliumOS 1.0beta1 "Vivid Vervet" - Release amd64 (20151109.1)
ProcCmdline: /usr/lib/xorg/Xorg -nolisten tcp -core -auth /var/run/slim.auth
__libc_start_main (main=0x55f7df0d4f00, argc=6, argv=0x7ffdc6e3d9a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdc6e3d998) at libc-start.c:289
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: Upgraded to xenial on 2016-02-10 (0 days ago)
To manage notifications about this bug go to: