metacity crashed with SIGSEGV in SmcCloseConnection()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
metacity (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
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
ProcVersionSign
Uname: Linux 2.6.32-18-generic x86_64
NonfreeKernelMo
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 <SmcCloseConnec
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_
?? () from /lib/libglib-
g_main_loop_run () from /lib/libglib-
Title: metacity crashed with SIGSEGV in SmcCloseConnect
UserGroups:
StacktraceTop: ice_messages ( context_ dispatch () 2.0.so. 0 2.0.so. 0
SmcCloseConnection (smcConn=0x0, count=0, reasonMsgs=0x0)
process_
g_main_
?? () from /lib/libglib-
g_main_loop_run () from /lib/libglib-