CSSH cause compiz crashed with SIGSEGV in CompWindow::id()

Bug #749497 reported by Dekel Amrani
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Unity
New
Undecided
Unassigned
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: unity

Running latest 11.04 Beta.
Unity 3D
trying to execute CSSH which worked well on 10.10 caused compiz to crash.

Dekel

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Sun Apr 3 19:45:32 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x43bef0 <_ZN10CompWindow2idEv>: mov 0x58(%rdi),%rax
 PC (0x0043bef0) ok
 source "0x58(%rdi)" (0x00000058) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 CompWindow::id() ()
 CompScreen::handleEvent(_XEvent*) ()
 PrivateCompositeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libcomposite.so
 CompScreen::handleEvent(_XEvent*) ()
 PrivateGLScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in CompWindow::id()
UpgradeStatus: Upgraded to natty on 2011-04-03 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Dekel Amrani (dekela) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

could be bug #747439 or similar

Revision history for this message
Mark Ulmer (markulmer) wrote :

Same as above, crash attempting to launch CSSH.

Revision history for this message
johnhamelink (johnhamelink) wrote :

Me too, always happens when launching CSSH (cluster SSH for those confused).

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.