Ubuntu
unity-system-compositor package

unity-system-compositor crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() resuming with two screend

Bug #1235876 reported by Colin Law on 2013-10-06

This bug report is a duplicate of: Bug #1237332: Fatal exceptions raised in a compositing thread have no usable stack trace. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unity-system-compositor (Ubuntu)	New	Undecided	Unassigned

Bug Description

On resume after suspend, with laptop screen and additional monitor I get a display with wallpaper but no launcher or panels, after a while it tells me I am running in low graphics mode, then it crashes. Suspend/resume is ok with only the laptop display.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-system-compositor 0.0.1+13.10.20131003.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sun Oct 6 08:58:09 2013
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard:
Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer Device [1558:0240]
InstallationDate: Installed on 2012-08-01 (430 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
MarkForUpload: True
ProcCmdline: /usr/sbin/unity-system-compositor --from-dm-fd 10 --to-dm-fd 13 --vt 7
ProcEnviron:

Signal: 6
SourcePackage: unity-system-compositor
StacktraceTop:
__gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
start_thread (arg=0xaa1feb40) at pthread_create.c:311
Title: unity-system-compositor crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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

Tags:

Revision history for this message

Colin Law (colin-law) wrote on 2013-10-06:

BootLog.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.3 KiB, text/plain; charset="utf-8")
LightDMLog.txt Edit (3.1 KiB, text/plain; charset="utf-8")
LightDMLogOld.txt Edit (4.1 KiB, text/plain; charset="utf-8")
UnitySystemCompositorLog.txt Edit (209 bytes, text/plain; charset="utf-8")
UnitySystemCompositorLogOld.txt Edit (447 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-10-06: 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 #1213583, 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.

information type:	Private → Public
tags:	removed: need-i386-retrace

Revision history for this message

Colin Law (colin-law) wrote on 2013-10-24:

Is this actually a dup of bug#1237332 (Fatal exceptions raised in the Mir code have no usable stack trace) or is it just that it is impossible to analyse this bug because 1237332 exists? Or to put it another way, if that bug is fixed will this one then also be automatically fixed?