ccsm crashed with KeyError in compizconfig.Plugin.ApplyStringExtensions (src/compizconfig.c:6780)(): '\xe0\xeb\xd0\x01'

[Jacobsallan]

ajacobs@ceshannon:~$ lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10
ajacobs@ceshannon:~$ apt-cache policy compizconfig-settings-manager
compizconfig-settings-manager:
  Installed: 0.9.5.92-0ubuntu1
  Candidate: 0.9.5.92-0ubuntu1
  Version table:
 *** 0.9.5.92-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages
        100 /var/lib/dpkg/status
Brought up compiz from the dash, clicked General, clicked General Options. Selected the Key bindings tab. Mouse movements across the right edge of the compiz settings manager panel triggered the scrollbar to appear and move a bit. Then apport reported that there was a problem in compiz.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: compizconfig-settings-manager 0.9.5.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Fri Aug 26 20:55:08 2011
ExecutablePath: /usr/bin/ccsm
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ccsm
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/ccsm']
SourcePackage: compizconfig-settings-manager
Title: ccsm crashed with KeyError in compizconfig.Plugin.ApplyStringExtensions (src/compizconfig.c:6780)(): '\xe0\xeb\xd0\x01'
UpgradeStatus: Upgraded to oneiric on 2011-08-24 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Jacobsallan (jacobsallan)]

Nearly repeatable. The character string changed to '\xc9\x0b\x02' in my next attempt to replicate this bug.

[Apport retracing service (apport)]

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 #832458, 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.