ccsm crashed with SIGSEGV in ccsCanDisablePlugin()

Bug #853427 reported by marcobra (Marco Braida)
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compizconfig-settings-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

just changing using ccsm windows decorator options because my unity is not working at all due windows decorator error

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: compizconfig-settings-manager 0.9.5.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sun Sep 18 21:18:30 2011
ExecutablePath: /usr/bin/ccsm
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110531.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ccsm
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x6d4b4a4 <ccsCanDisablePlugin+532>: movl $0x1,0xc(%eax)
 PC (0x06d4b4a4) ok
 source "$0x1" ok
 destination "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: compizconfig-settings-manager
StacktraceTop:
 ccsCanDisablePlugin () from /usr/lib/libcompizconfig.so.0
 ?? () from /usr/lib/python2.7/dist-packages/compizconfig.so
 ?? ()
 ?? ()
 PyEval_EvalFrameEx ()
Title: ccsm crashed with SIGSEGV in ccsCanDisablePlugin()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #833326, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.