GNOME Bugzilla – Bug 593929
Empathy 2.27.91.1 crashes at start -- connection-manager.c: No such file or directory.
Last modified: 2009-09-09 16:45:32 UTC
Empathy in gdb produces : ++++++++++++++++ GDB output ++++++++++++ [Thread debugging using libthread_db enabled] [New Thread 0x79f3b70 (LWP 28797)] (/usr/bin/empathy:28790): libebook-WARNING **: Can't find installed BookFactories (/usr/bin/empathy:28790): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed Program received signal SIGSEGV, Segmentation fault. tp_connection_manager_idle_read_manager_file (data=0x83f92d8) at connection-manager.c:1158 1158 connection-manager.c: No such file or directory. in connection-manager.c ++++++++++++++++ end of GDB output ++++++++++++ The main windows of Empathy is still open, but is empty. I can only close the windows. At this point, gdb is no more enthusiastic to help me : (gdb) thread apply all backtrace Cannot find new threads: generic error I'm using Empathy under Ubuntu-karmic with the ppa : deb http://ppa.launchpad.net/telepathy/ubuntu karmic main
Empathy has a different behavior if I'm connected in GoogleTalk (I mean : the wenb interface on gmail.com) or not in the same time. 1. If I first connect gmail.com, Empahty launches itself normally and works fine. Here is the output in gdb : (gdb) run Starting program: /usr/bin/empathy (no debugging symbols found) [... snip ...] (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb61a6b70 (LWP 5079)] (/usr/bin/empathy:4987): libebook-WARNING **: Can't find installed BookFactories (/usr/bin/empathy:4987): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed [Thread 0xb61a6b70 (LWP 5079) exited] Program exited normally. <--- at this point, I left Empathy in the usual way. 2. If I launch Empathy without being connected in gmail.com, the error in gdb is different : (gdb) run Starting program: /usr/bin/empathy (no debugging symbols found) [...] (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb61a6b70 (LWP 6166)] (/usr/bin/empathy:6156): libebook-WARNING **: Can't find installed BookFactories (/usr/bin/empathy:6156): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed Program received signal SIGSEGV, Segmentation fault. tp_connection_manager_idle_read_manager_file (data=0x86c1a98) at connection-manager.c:1158 1158 connection-manager.c: No such file or directory. in connection-manager.c (gdb) At this point, the contact list is open but crashed and the icon is not present in the tray. By the way, $ ps aux|grep empathy 153:kusbiste 6040 0.9 1.7 41472 36496 pts/1 S+ 08:40 0:00 gdb empathy 154:kusbiste 6156 0.4 1.1 97616 23216 pts/1 Tl 08:40 0:00 /usr/bin/empathy If I connect my gmail account in gmail.com, I see all my empathy's accounts as connected, but if I call myself, nothing happens. Now, I quit gdb : (gdb) quit The program is running. Quit anyway (and kill it)? (y or n) y At this point, Empathy seems closed. The icon is not present, gdb says that it killed Empathy and $ ps aux|grep empathy produces nothing. But gmail.com still sees me connected (even afer closing/opening) and if I receive a message (for example by connecting myself in gmail.com, or from someone else), Empathy gets crazy. It neverending opens and closes itself every tree seconds. No way to stop it apart of closing KDE.
This bug is also present in the official Ubuntu Karmic alpha-5 distribution. https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/424512
An automatic bug report which includes all the valuable informations is created downstream (Ubuntu) for the same bug : https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/425274
Thanks; it looks like that bug report is not public, could you change that, or copy/paste the details here?
An issue which could potentially trigger this crash has been fixed in telepathy-glib 0.7.36, is there a possiblity you can retest with that ?
The bug report on Ubuntu's launchapd is not *yet* public ;) This is due to the fact that the automatic reporting system uploads a full core dump. for privacy reasons, it is not public. In a second time, a backtrace will be automatically generated, the core dump will then be removed and the bug report will be turned to public.
In some way, the problem was fixed between September 7 and September 8. I got some updates for empathy, telepathy (and other related) from the ppa and it seems to work now. As far as I know, none of these updates was named "telepathy-glib". How can I check that I actually have telepathy-glib 0.7.36 ? As far as I am concerned, this bug can be closed now.
*** Bug 594614 has been marked as a duplicate of this bug. ***
This was a telepathy-glib bug.
*** Bug 593436 has been marked as a duplicate of this bug. ***