Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86PostProbe()

[Turbond]

Crashed on connecting with VNC Client. Using vnc4server.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: xserver-xorg-core 2:1.18.4-1ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 17 12:28:21 2017
ExecutablePath: /usr/lib/xorg/Xorg
InstallationDate: Installed on 2017-02-06 (38 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
ProcEnviron: PATH=(custom, no user)
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 xf86PostProbe ()
 InitOutput ()
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 OsAbort ()
 AbortServer ()
 FatalError ()
 xf86PostProbe ()
 InitOutput ()

[Launchpad Janitor (janitor)]

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

[Ken Mollerup (kenmollerup)]

I unfortunately installed Beignet after invoking the nvidia driver, then I had problems vith Nvidia so I reverted to nuevo graphics, but the problem persist!

[Alex Lohr (atl77)]

This usually happens for me when I login and the X session is started, which sends me back to the login. I have made the observation that this doesn't happen if a stable network connection is already present.

[Daniel Hollocher (chogydan)]

I've been getting this when waking from sleep. I have a weird experience before with sleep on this computer, where I was running linux mint 18.something, and I noticed that it wasn't going to sleep all the time. It was a weird thing where opening the laptop when a sleep was already initiated would pause the sleep from happening even if the laptop was closed again. I was playing with this, opening and closing the laptop when I noticed some errors. It wasn't recovering, and things were getting weird, so I decided to reboot... I never did boot off that ssd again. Luckily, I was able to read ALL the data off the drive, just couldn't write to it, or boot off it.

So I'm not going to test this. Maybe there is some weird hw bug. Hopefully me sharing this story provides some kind of useful data point.

[gaminder (gaminder)]

I'm not sure but I think in my case this happens after starting up from standby.

[Caner Çelik (anafor)]

I have been facing this issue for a couple of months and still couldn't find any solution.

[Paul White (paulw2u)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

[Launchpad Janitor (janitor)]

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