compiz crashed with SIGSEGV in ccsStringToModifiers()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crash reported by apport
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CheckboxSubmission: 93065c6f67bd29c
CheckboxSystem: b1865df84255b87
Date: Sun Sep 16 21:55:58 2012
DistUpgraded: 2012-09-16 22:32:30,421 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device [1179:0005]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
MachineType: TOSHIBA PORTEGE R830
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? () from /lib/x86_
?? ()
?? ()
ccsStringToMod
?? () from /usr/lib/
Title: compiz crashed with SIGSEGV in ccsStringToModi
UpgradeStatus: Upgraded to quantal on 2012-09-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/31/2012
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.90
dmi.board.
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: PORTEGE R830
dmi.product.
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1051697, 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.