Comment 0 for bug 1584894

Revision history for this message
Huck-bernhard (huck-bernhard) wrote : unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()

can not login to Unity8

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
Date: Mon May 23 19:20:43 2016
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-05-19 (3 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160519)
ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
ProcEnviron:

Signal: 6
SourcePackage: unity-system-compositor
StacktraceTop:
 mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.8
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

version.libdrm: libdrm2 2.4.68-1
version.lightdm: lightdm 1.19.0-0ubuntu1
version.mesa: libegl1-mesa-dev N/A