compiz crashed with SIGSEGV in ccsStringToModifiers()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Just upgraded from 12.04 to 12.10, launched the desktop after reboot and it crashed generated this crash report
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-31-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sat Sep 8 11:47:50 2012
DistUpgraded: 2012-09-08 13:16:21,194 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
ExecutableTimes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device [1179:0009]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: TOSHIBA SATELLITE Z830
ProcCmdline: compiz
ProcCwd: /home/czajkowski
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-08 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/09/2011
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.40
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: SATELLITE Z830
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 #1047827, 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.