compiz crashed with SIGSEGV in assign_to_own()

Bug #1302891 reported by Favio D'Ercole
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Confirmed
Medium
Unassigned
unity (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

on ubuntu 14.04 beta

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140403-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 4 20:16:26 2014
Disassembly: => 0x0: No se puede acceder a la memoria en la dirección 0x0
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-03-29 (5 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: No se puede acceder a la memoria en la dirección 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
 source "0x0" (0x00000000) not located in a known VMA region (needed readable region)!
SegvReason:
 executing NULL VMA
 reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? ()
 CompAction::initiate() const () from /usr/lib/libcompiz_core.so.ABI-20140123
 unity::MultiActionList::Initiate(std::string const&, std::vector<CompOption, std::allocator<CompOption> > const&, int) const () from /usr/lib/compiz/libunityshell.so
 unity::MultiActionList::InitiateAll(std::vector<CompOption, std::allocator<CompOption> > const&, int) const () from /usr/lib/compiz/libunityshell.so
 unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in CompAction::initiate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Favio D'Ercole (fndercole) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 assign_to_own (f=..., this=0x7fff19b97bc0) at /usr/include/boost/function/function_template.hpp:909
 function3 (f=..., this=0x7fff19b97bc0) at /usr/include/boost/function/function_template.hpp:749
 function (f=..., this=0x7fff19b97bc0) at /usr/include/boost/function/function_template.hpp:1089
 CompAction::initiate (this=<optimized out>) at /build/buildd/compiz-0.9.11+14.04.20140328/src/action.cpp:360

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 (Ubuntu):
importance: Undecided → Medium
summary: - compiz crashed with SIGSEGV in CompAction::initiate()
+ compiz crashed with SIGSEGV in assign_to_own()
tags: removed: need-amd64-retrace
Stephen M. Webb (bregma)
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 (Ubuntu):
status: New → Confirmed
Changed in unity:
importance: Undecided → Medium
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.