unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()

Bug #1632077 reported by Luca Ciavatta
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-system-compositor (Ubuntu)
New
Medium
Unassigned

Bug Description

1) Ubuntu 16.10 ***
2) unity-system-compositor 0.7.1+16.10.20160909.1-0ubuntu1
3) At login screen, I have tried to enter in Unity 8 session and I expected to enter in it.
4) Bring back at login screen

*** System virtualized under VirtualBox 5.1.6

The issue report has appeared after a new login in a Unity 7 session.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: unity-system-compositor 0.7.1+16.10.20160909.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
Uname: Linux 4.8.0-19-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Mon Oct 10 21:11:22 2016
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2015-12-22 (293 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --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.6
 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
UpgradeStatus: Upgraded to yakkety on 2016-10-07 (3 days ago)
UserGroups:

version.libdrm: libdrm2 2.4.70-1
version.lightdm: lightdm 1.19.5-0ubuntu1
version.mesa: libegl1-mesa-dev 12.0.3-1ubuntu2

Revision history for this message
Luca Ciavatta (cialu) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 mir::fatal_error_abort(char const*, ...) (reason=0x7fd55af5f98c "Failed to schedule page flip") at ./src/common/fatal/fatal.cpp:43
 ?? () from /tmp/apport_sandbox_FukxsO/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10
 mir::compositor::CompositingFunctor::operator()() (this=0x5647ef5b0840) at ./src/server/compositor/multi_threaded_compositor.cpp:143
 operator() () at /usr/include/c++/6/functional:2136
 execute (this=0x7fd553a80c70) at ./src/server/thread/basic_thread_pool.cpp:40

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity-system-compositor (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1584894, so it 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. Feel free to continue to report any other bugs you may find.

information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.