compiz crashed with SIGSEGV in PluginClassHandler<DecorWindow, CompWindow, 0>::get()

Bug #749298 reported by Fred
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: compiz

i dont remember

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4git20110322-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Apr 3 14:15:56 2011
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en
 LANG=en_US.utf8
 LC_MESSAGES=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature_: Ubuntu 2.6.38-7.39-generic 2.6.38
SegvAnalysis:
 Segfault happened at: 0x7f46c54dc67a <_ZN18PluginClassHandlerI11DecorWindow10CompWindowLi0EE3getEPS1_+266>: mov 0x30(%rbp),%rax
 PC (0x7f46c54dc67a) ok
 source "0x30(%rbp)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 PluginClassHandler<DecorWindow, CompWindow, 0>::get(CompWindow*) () from /usr/lib/compiz/libdecor.so
 DecorScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libdecor.so
 CompScreen::handleEvent(_XEvent*) ()
 MoveScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libmove.so
 CompScreen::handleEvent(_XEvent*) ()
Title: compiz crashed with SIGSEGV in PluginClassHandler<DecorWindow, CompWindow, 0>::get()
UpgradeStatus: Upgraded to natty on 2011-03-28 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1

Revision history for this message
Fred (eldmannen+launchpad) wrote :
tags: added: compiz-0.9
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.