compiz crashed with SIGSEGV in getCompPluginVTable20090315_unitymtgrabhandles()

[John S. Gruber]

In qemu with default Cirrus virtual adapter. Compiz fails to start--must run different DE.

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
CurrentDmesg:
 [ 36.768694] init: plymouth-stop pre-start process (1205) terminated with status 1
 [ 47.841498] colord-sane[1420]: segfault at 0 ip b73c3f2f sp bfac69e0 error 4 in libc-2.15.so[b7315000+19f000]
 [ 62.910143] compiz[1645]: segfault at 0 ip b2b38610 sp bf8d2550 error 4 in libunitymtgrabhandles.so[b2b23000+30000]
 [ 72.130551] compiz[1745]: segfault at 0 ip b2ab5610 sp bf8302f0 error 4 in libunitymtgrabhandles.so[b2aa0000+30000]
Date: Sat Sep 1 16:02:15 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc Device [1af4:1100]
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120901)
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: Bochs Bochs
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=405699d4-1c73-468b-8b95-d61e79775f21 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb2b38610 <getCompPluginVTable20090315_unitymtgrabhandles+32>: mov (%esi),%eax
 PC (0xb2b38610) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 getCompPluginVTable20090315_unitymtgrabhandles () from /usr/lib/compiz/libunitymtgrabhandles.so
 ?? () from /usr/lib/libcompiz_core.so.ABI-20120603
 CompPlugin::load(char const*) () from /usr/lib/libcompiz_core.so.ABI-20120603
 compiz::private_screen::PluginManager::updatePlugins(CompScreen*, std::vector<CompOption::Value, std::allocator<CompOption::Value> > const&) () from /usr/lib/libcompiz_core.so.ABI-20120603
 PrivateScreen::processEvents() () from /usr/lib/libcompiz_core.so.ABI-20120603
Title: compiz crashed with SIGSEGV in getCompPluginVTable20090315_unitymtgrabhandles()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
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

[Apport retracing service (apport)]

StacktraceTop:
 unity::MT::X11GrabHandleImpl::lockPosition (this=0x50706d6f, x=1768387948, y=1632917102, flags=845507682) at /build/buildd/unity-6.4.0/plugins/unity-mt-grab-handles/src/unity-mt-grab-handles.cpp:121
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Actually this looks kind of like bug 1043143.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christopher Townsend (townsend)]

This is a rather old bug and it sure looks like it doesn't occur anymore. Since it's been some time since a crash like this has been reported, it seems it's been fixed some release ago and I'm marking as such.

If it does still occur, we can reopen this bug report or open a new one.