Red Hat Bugzilla – Bug 457659
telepathy-gabble 0.7.7 hits an assertion on connect
Last modified: 2008-08-07 13:27:02 EDT
Description of problem:
Everytime I start empathy on F10 it will start, connect, show part of the buddylist then disconnect. The following can be seen in the terminal.
** (empathy:4262): DEBUG: mission_control_get_presence_actual: MC not running.
** (empathy:4262): DEBUG: mission_control_get_presence_message_actual: MC not running.
** (empathy:4262): DEBUG: mission_control_get_online_connections: MC not running.
** (empathy:4262): DEBUG: mission_control_get_connection_status: MC not running.
** (empathy:4262): DEBUG: mission_control_get_tpconnection: MC not running.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start empathy
Does this happen with all accounts, or only specific ones? (If so, which ones?)
I just rebuilt the Rawhide one for my F9 box and it seems to be functioning nicely. What EVRs of the telepathy stack are you using? ("rpm -qa telepathy*" should tell you.)
When did you first notice this issue, and what packages did you update on or about that time? Maybe something in one of its deps somewhere is acting up... :/
I cleanly installed empathy and telepathy (I am only using gabble with gtalk), cleaned the profile and configuration file. Same problem.
Just might be related to:
This is indeed related to telepathy-gabble, reassigning. Upstream bug report linked in #2 now contains a workaround. The reason you can't trigger it on F9 is that the glib2 is Development is more picky about the input it seems.
a) Back down to 0.7.6
b) patch 0.7.7 with snippet from upstream
c) wait for 0.7.8
I would favor b or a, keeping jabber working would be advisable, especially since empathy is now part of GNOME.