metacity crashed with SIGSEGV in SmcCloseConnection()

[Dirk Tas]

Binary package hint: metacity

metacity crashed after trying to open my miniblog account via the me-menu

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: metacity 1:2.28.1-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Mar 31 07:02:45 2010
ExecutablePath: /usr/bin/metacity
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: metacity
ProcEnviron:
 LANG=nl_BE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7fdd17b84719 <SmcCloseConnection+25>: mov 0x8(%rdi),%r14
 PC (0x7fdd17b84719) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%r14" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: metacity
StacktraceTop:
 SmcCloseConnection () from /usr/lib/libSM.so.6
 ?? ()
 g_main_context_dispatch ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0
Title: metacity crashed with SIGSEGV in SmcCloseConnection()
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 SmcCloseConnection (smcConn=0x0, count=0, reasonMsgs=0x0)
 process_ice_messages (
 g_main_context_dispatch ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.