mission-control-5 crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-mission-control-5 (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: telepathy-
* Ubuntu Lucid Lynx 10.04 Beta1
* telepathy-
I wasn't doing anything specific with empathy/telepathy when this error message showed up. I was just signed in to my msn and jabber accounts.
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: telepathy-
ProcVersionSign
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Sun Apr 4 20:56:10 2010
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x431d36: mov (%rdi),%ebx
PC (0x00431d36) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-
StacktraceTop:
?? ()
?? ()
g_closure_invoke ()
?? () from /usr/lib/
g_signal_
Title: mission-control-5 crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
StacktraceTop: error_string (error=0x0) at mcd-misc.c:70 operation_ channel_ aborted_ cb ( libgobject- 2.0.so. 0 emit_valist ()
_mcd_build_
mcd_dispatch_
g_closure_invoke ()
?? () from /usr/lib/
g_signal_