compiz crashed with SIGSEGV

[Akhila]

Compiz closed unexpectedly when Time and Date settings was opened.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
CurrentDmesg:
 [ 1463.121870] show_signal_msg: 18 callbacks suppressed
 [ 1463.121898] compiz[1655]: segfault at f80e1c78 ip b755df21 sp bfe64a64 error 4 in libc-2.15.so[b7429000+19f000]
Date: Tue Sep 11 19:39:24 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller])
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120911)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic root=UUID=4490dcba-b934-4ca5-ad7b-83e85959dc0c ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb755df21: movdqu 0x30(%esi),%xmm3
 PC (0xb755df21) ok
 source "0x30(%esi)" (0xf80e1c70) not located in a known VMA region (needed readable region)!
 destination "%xmm3" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
Stacktrace:
 #0 0xb755df21 in ?? () from /lib/i386-linux-gnu/libc.so.6
 No symbol table info available.
 #1 0xb4bbd000 in ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
Title: compiz crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.6-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1

[Apport retracing service (apport)]

Stacktrace:
 #0 __memmove_ssse3 () at ../sysdeps/i386/i686/multiarch/memcpy-ssse3.S:2243
 No locals.
 #1 0xb4bbd000 in ?? () from /tmp/tmpN5BGCX/usr/lib/i386-linux-gnu/dri/swrast_dri.so
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceSource:
 #0 __memmove_ssse3 () at ../sysdeps/i386/i686/multiarch/memcpy-ssse3.S:2243
   [Error: ../sysdeps/i386/i686/multiarch/memcpy-ssse3.S was not found in source tree]
 #1 0xb4bbd000 in ?? () from /tmp/tmpN5BGCX/usr/lib/i386-linux-gnu/dri/swrast_dri.so
StacktraceTop: ?? () from /tmp/tmpN5BGCX/usr/lib/i386-linux-gnu/dri/swrast_dri.so

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1049192

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 927168, so it 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. Feel free to continue to report any other bugs you may find.