Bug 473538 - Adding a second account make empathy crash
Summary: Adding a second account make empathy crash
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: loudmouth
Version: 10
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-29 08:10 UTC by Eric Tanguy
Modified: 2018-04-11 08:18 UTC (History)
6 users (show)

Fixed In Version: 1.4.3-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-06 02:14:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
backtrace from bug-buddy (16.04 KB, text/plain)
2008-12-02 07:13 UTC, Matěj Cepl
no flags Details
crash in telepathy-gabble (1.97 KB, text/plain)
2008-12-02 07:50 UTC, Matěj Cepl
no flags Details
debugging information from empathy (9.65 KB, text/plain)
2008-12-02 07:51 UTC, Matěj Cepl
no flags Details
debugging information from telepathy-gabble (9.17 KB, text/plain)
2008-12-02 07:52 UTC, Matěj Cepl
no flags Details

Description Eric Tanguy 2008-11-29 08:10:01 UTC
Description of problem:

All is in the summary


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Peter Gordon 2008-11-29 10:37:20 UTC
Is it only a second account of a specific protocol or does adding any more than one account cause this crash?

Comment 2 Eric Tanguy 2008-11-29 10:43:47 UTC
I don' t know because i only have 2 jabber account

Comment 3 Eric Tanguy 2008-11-29 16:25:05 UTC
In fact it's when you add the second account it's when you activate it that empathy crash

Comment 4 Matěj Cepl 2008-12-01 23:42:33 UTC
Cannot reproduce with the upstream SVN 1941.

Comment 5 Matěj Cepl 2008-12-02 07:07:55 UTC
Sorry, this apparently has not been fixed. For me adding fourth jabber account was kind of painful (empathy crashed couple of times), but then it somehow begun work. Adding fifth account (internal RH Jabber server) seems to be just not working. If the account is disabled empathy starts without a problem, but immediately after it has been started, I get this crash.

Comment 6 Matěj Cepl 2008-12-02 07:13:26 UTC
Created attachment 325331 [details]
backtrace from bug-buddy

Actually, it looks to my stupid eye like the trouble is somewhere down the stack (obviously I have SVN 1941 version of empathy, not the one from Rawhide packages, so I cannot blame packaged version of empathy for this).

Also, bug-buddy crashed on the way as well, so I was not able to poste the backtrace upstream. Will file different bug about that.

Comment 7 Matěj Cepl 2008-12-02 07:27:20 UTC
bug 474092 about bug-buddy crashes filed.

Forgot to add versions of telepathy packages:
[matej@viklef ~]$ rpm -qa telepathy\*|grep -v -E -- '-de(vel|buginfo)'
telepathy-stream-engine-0.5.3-2.fc10.i386
telepathy-filesystem-0.0.1-2.fc8.noarch
telepathy-salut-0.3.5-1.fc10.i386
telepathy-glib-0.7.17-1.fc10.i386
telepathy-gabble-0.7.12-1.fc10.i386
telepathy-haze-0.2.1-1.fc10.i386
telepathy-mission-control-4.67-1.fc10.i386
telepathy-idle-0.1.2-3.fc9.i386
[matej@viklef ~]$

Comment 8 Matěj Cepl 2008-12-02 07:50:22 UTC
Created attachment 325333 [details]
crash in telepathy-gabble

When trying to reproduce with all debugging stuff from http://live.gnome.org/Empathy/Debugging I got this IMHO much nicer backtrace from telepathy-gabble pointing to libloudmouth.

Comment 9 Matěj Cepl 2008-12-02 07:51:41 UTC
Created attachment 325335 [details]
debugging information from empathy

Comment 10 Matěj Cepl 2008-12-02 07:52:20 UTC
Created attachment 325336 [details]
debugging information from telepathy-gabble

Comment 12 Matěj Cepl 2008-12-02 10:16:26 UTC
should be fixed in loudmouth 1.4.4 (not yet released)

Comment 13 Brian Pepple 2008-12-02 14:48:08 UTC
(In reply to comment #11)
> Related bugs are apparently in
> http://bugs.freedesktop.org/show_bug.cgi?id=16994
> and
> http://loudmouth.lighthouseapp.com/projects/17276-libloudmouth/tickets/33-crash-when-async-dns-resolv-fails

These bugs are fixed in loudmouth-1.4.3-3.fc11 and loudmouth-1.4.3-1.fc10.

Comment 14 Eric Tanguy 2008-12-02 18:02:10 UTC
I update to loudmouth-1.4.3-1.fc10 and the problem seems resolved.
So you can close the bug if you can confirm this.


Note You need to log in before you can comment on or make changes to this bug.