compiz crashed with SIGSEGV in getCompPluginVTable20090315_unitymtgrabhandles()

[Gvozdik Artem]

Unstable 12.10 system, a lot of things such as compiz doesn`t simply run as expected.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2
Uname: Linux 3.5.0-12-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012
 GCC version: gcc version 4.7.1 20120814 (prerelease) (Ubuntu/Linaro 4.7.1-7ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Sun Sep 2 12:39:03 2012
DistUpgraded: 2012-08-07 18:53:40,681 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
 nvidia-current, 304.43, 3.5.0-12-generic, x86_64: installed
 nvidia-current-updates, 304.43, 3.5.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!)
 virtualbox, 4.1.18, 3.5.0-12-generic, x86_64: installed
 virtualbox, 4.1.18, 3.5.0-9-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Giga-byte Technology Device [1458:3515]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
JockeyStatus:
 kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use)
 kmod:nvidia_current_updates - nvidia_current_updates (Proprietary, Enabled, Not in use)
MachineType: MSI MS-7623
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-12-generic root=UUID=347c4401-7eda-4573-b763-51fbf9d20169 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f8b08b03a15 <getCompPluginVTable20090315_unitymtgrabhandles+21>: mov (%rbx),%rax
 PC (0x7f8b08b03a15) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" 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: Upgraded to quantal on 2012-08-07 (25 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XorgConf:
 Section "Device"
  Identifier "Default Device"
  Option "NoLogo" "True"
 EndSection
dmi.bios.date: 11/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V25.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 880GMA-E55 (MS-7623)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 5.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/22/2010:svnMSI:pnMS-7623:pvr5.0:rvnMSI:rn880GMA-E55(MS-7623):rvr5.0:cvnMSI:ct3:cvr5.0:
dmi.product.name: MS-7623
dmi.product.version: 5.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
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:
 X11TextureFactory (this=<optimized out>) at /build/buildd/unity-6.4.0/plugins/unity-mt-grab-handles/src/unity-mt-grab-handles.h:56
 UnityMTGrabHandlesScreen::UnityMTGrabHandlesScreen (this=0x0, s=<optimized out>) at /build/buildd/unity-6.4.0/plugins/unity-mt-grab-handles/src/unity-mt-grab-handles.cpp:788
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

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:

outdated debug symbol package for unity: package version 6.4.0-0ubuntu2 dbgsym version 6.4.0-0ubuntu1

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!

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