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

Bug #1630472 reported by Victor gonzalez
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
unity-system-compositor (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Just after reboot when running unity8 on qemu

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: unity-system-compositor 0.7.1+16.10.20160909.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Oct 5 09:01:48 2016
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard:
 Device [1234:1111] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc Device [1af4:1100]
InstallationDate: Installed on 2016-10-03 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
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-04 (0 days ago)
UserGroups:

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

Revision history for this message
Victor gonzalez (victor-gonzalez-0) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 mir::fatal_error_abort(char const*, ...) (reason=0x7f6e290b698c "Failed to schedule page flip") at ./src/common/fatal/fatal.cpp:43
 ?? () from /tmp/apport_sandbox_tJpuSC/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10
 mir::compositor::CompositingFunctor::operator()() (this=0x561343bea110) at ./src/server/compositor/multi_threaded_compositor.cpp:143
 operator() () at /usr/include/c++/6/functional:2136
 execute (this=0x7f6e22bd9c70) 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
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity-system-compositor (Ubuntu):
status: New → Confirmed
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.