mission-control-5 crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-mission-control-5 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: telepathy-
the program crash but nothing appear in the screen
ProblemType: Crash
Architecture: amd64
Date: Wed Mar 17 22:10:05 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelMo
Package: telepathy-
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=fr_CA:fr
LANG=fr_CA.utf8
ProcVersionSign
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()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fuse netdev plugdev video
visibility: | private → public |
Just had the same crash on Lucid, when double clicking on a contact to open a chat window.
After the crash, no new windows want to open, even after restarting empathy.