Xorg crashed with SIGABRT in OsAbort()

StacktraceTop:
 OsAbort () at ../../os/utils.c:1299
 FatalError (f=f@entry=0x7f4741d9ab18 "%s: VT_ACTIVATE failed: %s\n") at ../../os/log.c:911
 switch_to (vt=7, from=from@entry=0x7f4741d9aba1 "xf86CloseConsole") at ../../../../../hw/xfree86/os-support/linux/lnx_init.c:72
 xf86CloseConsole () at ../../../../../hw/xfree86/os-support/linux/lnx_init.c:308
 ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at ../../../../hw/xfree86/common/xf86Init.c:1106

Status changed to 'Confirmed' because the bug affects multiple users.

Donn Morrison, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1237904

this bug issue in ubuntu 15.10 for this time

I understand that this is marked as invalid, but it affects many people and is triggered by seemingly nothing by other than restart.

I do not understand why this is marked as invalid. It affects >100 people and I cannot see any questions not answered by the people affected.

Found 2 VTs used by Xorg (vt2 & vt7):

:~$ ps -aef |grep dm |grep X
root 1491 1484 4 22:43 tty7 00:00:04 /usr/bin/X vt7 -displayfd 3 -auth /run/user/116/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3
root 1865 1861 3 22:43 tty2 00:00:02 /usr/bin/X vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3

tty7 reserved by gdm (user 116) ;
:~$ id 116
uid=116(gdm) gid=124(gdm) groupes=124(gdm)

I will check with lightdm

The report in /var/log/Xorg.0.log:

"_XSERVTransMakeAllCOTSServerListeners: server already running"

suggests the system (user: gdm, uid: 116) display manager X server on VT7 owns/uses the socket in "/tmp/.X11-unix/" which prevents the user (uid:1000) display manager on VT2 from using the same socket.

Package: xserver-xorg-core 2:1.17.2-1ubuntu9
ProcCmdline: /usr/bin/X vt7 -displayfd 3 -auth /run/user/120/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3

This bug was fixed in the package xorg-server - 2:1.17.2-1ubuntu10

---------------
xorg-server (2:1.17.2-1ubuntu10) xenial; urgency=medium

  * debian/patches:
    - linux-Do-not-call-FatalError-from-xf86CloseConsole.patch: Fix crashers
      often occuring on shutdown (LP: #1237904)
    - xmir.patch: Fix typo causing FTBFS

 -- Tim Lunn <email address hidden> Mon, 26 Oct 2015 12:24:30 +1100

uploaded to the queue

Hello Donn, or anyone else affected,

Accepted xorg-server into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg-server/2:1.17.2-1ubuntu9.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tested as per testcase, did not encounter any crashed, tagging verification-done

This bug was fixed in the package xorg-server - 2:1.17.2-1ubuntu9.1

---------------
xorg-server (2:1.17.2-1ubuntu9.1) wily; urgency=medium

  * debian/patches:
    - linux-Do-not-call-FatalError-from-xf86CloseConsole.patch: Fix crashers
      often occuring on shutdown (LP: #1237904)
    - xmir.patch: Fix typo causing FTBFS (LP: #1509005)

 -- Tim Lunn <email address hidden> Mon, 26 Oct 2015 12:24:30 +1100

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.