compiz crashed with SIGSEGV in __memmove_ssse3_rep, under Virtualbox

[meanpt]

opened the dash, typed in terminal, opened the terminal and the crash was reported
Hw: virtualbox 4.1.20 runing under windows 7

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8+bzr3319-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic i686
ApportVersion: 2.5.1-0ubuntu2
Architecture: i386
CurrentDmesg:
 [ 17.436542] IPv6: ADDRCONF(NETDEV_UP): p2p1: link is not ready
 [ 17.436808] IPv6: ADDRCONF(NETDEV_CHANGE): p2p1: link becomes ready
Date: Sun Aug 26 19:06:32 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: virtualbox-guest, 4.1.18, 3.5.0-11-generic, i686: installed
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 (20120826)
Lsusb:
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=9c839db2-fecc-42cf-bf8b-aadf803ae65d ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb74c5021: movdqu 0x30(%esi),%xmm3
 PC (0xb74c5021) ok
 source "0x30(%esi)" (0x2c27a550) not located in a known VMA region (needed readable region)!
 destination "%xmm3" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
Stacktrace:
 #0 0xb74c5021 in ?? () from /lib/i386-linux-gnu/libc.so.6
 No symbol table info available.
 #1 0xb4c0f000 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+bzr3319-0ubuntu2
version.libdrm2: libdrm2 2.4.38-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2
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.3-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1

[Apport retracing service (apport)]

Stacktrace:
 #0 __memmove_ssse3_rep () at ../sysdeps/i386/i686/multiarch/memcpy-ssse3-rep.S:1803
 No locals.
 #1 0xb4c0f000 in ?? () from /tmp/tmpOYa06N/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_rep () at ../sysdeps/i386/i686/multiarch/memcpy-ssse3-rep.S:1803
   [Error: ../sysdeps/i386/i686/multiarch/memcpy-ssse3-rep.S was not found in source tree]
 #1 0xb4c0f000 in ?? () from /tmp/tmpOYa06N/usr/lib/i386-linux-gnu/dri/swrast_dri.so
StacktraceTop: ?? () from /tmp/tmpOYa06N/usr/lib/i386-linux-gnu/dri/swrast_dri.so

[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.