compiz crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Occured after update without restarting.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8+
ProcVersionSign
Uname: Linux 3.5.0-12-generic x86_64
ApportVersion: 2.5.1-0ubuntu3
Architecture: amd64
Date: Wed Aug 29 17:46:12 2012
DistUpgraded: 2012-07-20 09:33:23,464 WARNING can't import view 'DistUpgradeVie
DistroCodename: quantal
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
GraphicsCard:
NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Device [196e:0915]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: System manufacturer P5QL PRO
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f151e0f7ba0: movdqu -0x10(%
PC (0x7f151e0f7ba0) ok
source "-0x10(
destination "%xmm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? () from /lib/x86_
?? () from /usr/lib/
?? ()
?? ()
?? ()
Title: compiz crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-07-20 (40 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XorgConf:
dmi.bios.date: 11/28/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0902
dmi.board.
dmi.board.name: P5QL PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5QL PRO
dmi.product.
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.8+
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.38+
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 #1043505, 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.