Ubuntu
unity package

compiz crashed with SIGSEGV in memmove() from reference_exec() from signal_exec() sigc::internal::signal_emit0<void, sigc::nil>::emit(sigc::internal::signal_impl*) () from /usr/lib/libunity-core-6.0.so.5

Bug #1062483 reported by Cormac on 2012-10-05

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Unity	Invalid	Undecided	Unassigned
	unity (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Crash happened on startup after updating 12.10 on 5 Oct 12

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: libunity-core-6.0-5 6.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
Date: Thu Oct 4 17:14:33 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdline: compiz
Signal: 11
SourcePackage: unity
StacktraceTop:
?? () from /lib/i386-linux-gnu/libc.so.6
sigc::internal::signal_emit0<void, sigc::nil>::emit(sigc::internal::signal_impl*) () from /usr/lib/libunity-core-6.0.so.5
?? ()
?? ()
Title: compiz crashed with SIGSEGV in sigc::internal::signal_emit0<void, sigc::nil>::emit()
UpgradeStatus: Upgraded to quantal on 2012-09-06 (28 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Cormac (cormac-wilcox) wrote on 2012-10-05:

#1

Dependencies.txt Edit (5.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (619 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (308 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (50.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (796 bytes, text/plain; charset="utf-8")
Registers.txt Edit (509 bytes, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (200 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (374 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-05:

#2

StacktraceTop:
reference_exec (this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/signal_base.h:68
signal_exec (sig=0x0, this=0xbfab914c) at /usr/include/sigc++-2.0/sigc++/signal_base.h:160
sigc::internal::signal_emit0<void, sigc::nil>::emit (impl=0x0) at /usr/include/sigc++-2.0/sigc++/signal.h:769
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-05: Stacktrace.txt

#3

Stacktrace.txt Edit (649 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-05: StacktraceSource.txt

#4

StacktraceSource.txt Edit (777 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-05: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (9.2 KiB, text/plain)

Changed in unity (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Daniel van Vugt (vanvugt) on 2012-10-08

summary:	compiz crashed with SIGSEGV in sigc::internal::signal_emit0<void, - sigc::nil>::emit() + sigc::nil>::emit(sigc::internal::signal_impl*) () from + /usr/lib/libunity-core-6.0.so.5
summary:	- compiz crashed with SIGSEGV in sigc::internal::signal_emit0<void, + compiz crashed with SIGSEGV in memmove() from reference_exec() from + signal_exec() sigc::internal::signal_emit0<void, sigc::nil>::emit(sigc::internal::signal_impl*) () from /usr/lib/libunity-core-6.0.so.5
visibility:	private → public

Revision history for this message

Bilal Akhtar (bilalakhtar) wrote on 2012-10-12:

#6

Did the crash happen on startup, or did the dialog come up at startup? Often, I've seen apport dialogues popping up after login, which should have popped in the previous session.

Revision history for this message

Cormac (cormac-wilcox) wrote on 2012-10-13:

#7

It dialogue appeared on start up so I cannot tell if it happened then or if it was a delayed message.

Revision history for this message

Will Cooke (willcooke) wrote on 2015-08-26:

#8

Sorry folks, but as part of the bug clean up ahead of 16.04 I'm marking this as invalid because it affects an Ubuntu release which is now unsupported. If you can still recreate this bug in a supported release please do open a new bug and we can triage it for consideration in the 16.04 development cycle.

Changed in unity:
status:	New → Invalid
Changed in unity (Ubuntu):
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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