compiz crashed with SIGSEGV in g_closure_invoke()

[Susumu Tanimura]

Binary package hint: compiz

When I switched from a virtual console (with jfbterm) to an usual desktop, this crash occurred.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-7.35-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] ディレクトリです: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.30 Fri Feb 25 14:34:55 PST 2011
 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-6ubuntu4)
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: None
Date: Sat Mar 19 10:12:49 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
 nvidia-current, 270.30, 2.6.38-7-generic, x86_64: installed
 virtualbox-ose, 4.0.4, 2.6.38-7-generic, x86_64: installed
 virtualbox-ose, 4.0.4, 2.6.38-6-generic, x86_64: installed
 virtualbox-ose, 4.0.4, 2.6.38-5-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard: nVidia Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
JockeyStatus: xorg:nvidia_current - NVIDIAの高性能グラフィックスドライバ (プロプライエタリ, 有効にする, 使用中)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=ja_JP:en_US:en
 PATH=(custom, user)
 LANG=ja_JP.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=4fefd307-dd58-40e6-9a99-8e15258e5e73 ro quiet splash vt.handoff=7
ProcVersionSignature_: Ubuntu 2.6.38-7.35-generic 2.6.38
Renderer: Unknown
SegvAnalysis:
 Segfault happened at: 0x7f519306a81c <g_closure_invoke+348>: mov (%rbx),%rdx
 PC (0x7f519306a81c) ok
 source "(%rbx)" (0x01000000) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
Title: compiz crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/14/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BPX5810J.86B.0034.2010.0414.1511
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: WX58BP
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE64643-202
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrBPX5810J.86B.0034.2010.0414.1511:bd04/14/2010:svn:pn:pvr:rvnIntelCorporation:rnWX58BP:rvrAAE64643-202:cvn:ct2:cvr:
version.compiz: compiz 1:0.9.4-0ubuntu7
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6

[Apport retracing service (apport)]

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