Ubuntu
unity8 package

unity8 aborts on startup in image testing

Bug #1247163 reported by Michał Sawicz on 2013-11-01

This bug report is a duplicate of: Bug #1258655: Abort when blanking/unblanking screen; exception thrown from mir::graphics::android::HWCCommonDevice::mode(MirPowerMode). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unity8 (Ubuntu)	New	Undecided	Unassigned

Bug Description

This only happens on mako, and I couldn't reproduce locally yet.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity8 7.83+14.04.20131031-0ubuntu1
Uname: Linux 3.4.0-3-mako armv7l
Architecture: armhf
Date: Fri Nov 1 14:22:09 2013
ExecutablePath: /usr/bin/unity8
ExecutableTimestamp: 1383251436
ProcCmdline: unity8 -testability
ProcCwd: /home/phablet
Signal: 6
SourcePackage: unity8
StacktraceTop:
__gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
__cxxabiv1::__terminate (handler=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:38
std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:48
__cxxabiv1::__cxa_rethrow () at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:122
__exchange_and_add (__val=-1, __mem=0x1186) at /usr/include/c++/4.8/ext/atomicity.h:49
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video

Tags:

Revision history for this message

Michał Sawicz (saviq) wrote on 2013-11-01:

Dependencies.txt Edit (10.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (125 bytes, text/plain; charset="utf-8")
StacktraceSource.txt Edit (6.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-11-01: This bug is a duplicate

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