compiz crashed with SIGSEGV

Bug #1046314 reported by Pierre-Olivier Megret
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Crash in a fresh install in Virtualbox. No more information of how this crash occured.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.5.1-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Wed Sep 5 14:59:19 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: virtualbox-guest, 4.1.18, 3.5.0-13-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 (20120903)
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
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=c36e4514-95ca-4051-a593-931985ba5275 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb7599f21: movdqu 0x30(%esi),%xmm3
 PC (0xb7599f21) ok
 source "0x30(%esi)" (0x89440bd0) not located in a known VMA region (needed readable region)!
 destination "%xmm3" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
Stacktrace:
 #0 0xb7599f21 in ?? () from /lib/i386-linux-gnu/libc.so.6
 No symbol table info available.
 #1 0xb4b1c000 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.38-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3
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

Revision history for this message
Pierre-Olivier Megret (sorrodje) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 __memmove_ssse3 () at ../sysdeps/i386/i686/multiarch/memcpy-ssse3.S:2243
 No locals.
 #1 0xb4b1c000 in ?? () from /tmp/tmpAH4SHk/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 0xb4b1c000 in ?? () from /tmp/tmpAH4SHk/usr/lib/i386-linux-gnu/dri/swrast_dri.so
StacktraceTop: ?? () from /tmp/tmpAH4SHk/usr/lib/i386-linux-gnu/dri/swrast_dri.so

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in compiz (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libglib2.0-data version 2.33.10-0ubuntu3 required, but 2.33.12-2 is available
libglib2.0-0 version 2.33.10-0ubuntu3 required, but 2.33.12-2 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.