compiz crashed with SIGSEGV in CompAction::initiate()

Bug #742326 reported by Pieter Ennes
68
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Unity
Invalid
Medium
Unassigned
unity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: unity

binding a new compiz key

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.6.6-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Fri Mar 25 08:48:00 2011
Disassembly: => 0x30: Cannot access memory at address 0x30
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x30: Cannot access memory at address 0x30
 PC (0x00000030) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? ()
 CompAction::initiate() ()
 MultiActionList::InitiateAll(std::vector<CompOption, std::allocator<CompOption> >&, int) () from /usr/lib/compiz/libunityshell.so
 PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so
 SimpleLauncherIcon::ActivateLauncherIcon() () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in CompAction::initiate()
UpgradeStatus: Upgraded to natty on 2011-03-23 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Pieter Ennes (skion) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () at /usr/include/c++/4.5/bits/vector.tcc:301
 assign_to_own (this=<value optimized out>) at /usr/include/boost/function/function_template.hpp:888
 function3 (this=<value optimized out>) at /usr/include/boost/function/function_template.hpp:749
 function (this=<value optimized out>) at /usr/include/boost/function/function_template.hpp:1084
 CompAction::initiate (this=<value optimized out>) at /build/buildd/compiz-0.9.4git20110322/src/action.cpp:336

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

what do you mean exactly by "binding a new compiz key", can you provide some step by step description please?

Changed in unity:
status: New → Incomplete
Changed in unity (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in unity:
importance: Undecided → Medium
status: Incomplete → Invalid
Changed in unity (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Renji (romd996) wrote :

This happened to me when I was creating a new bind to put a window on other window in compizconfig-settings-manager.
I have a 2 monitor setup and I have to move windows across screens.
The "Put pointer" was enabled at '<Super> + z' when I was adding a bind for move window to other output. This is when the crash happened.
After unity restarted I disabled 'put pointer' and I enabled the keyboard bind in the put plugin. This time it did not crash.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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