After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 632479 - Disabling an account while connected doesn't update the rooster
Disabling an account while connected doesn't update the rooster
Status: RESOLVED DUPLICATE of bug 629082
Product: folks
Classification: Platform
Component: Telepathy backend
0.2.x
Other Linux
: Normal normal
: Unset
Assigned To: folks-maint
folks-maint
Depends on:
Blocks:
 
 
Reported: 2010-10-18 16:56 UTC by Juan J. Martinez
Modified: 2010-11-14 22:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Juan J. Martinez 2010-10-18 16:56:30 UTC
When disabling an account while connected, instead of removing the contacts associated to that account from the rooster automatically, the contacts remain in the rooster.

I have the contacts in a group associated to the disabled account, and the group name changes to 'Ungrouped', but the contacts remain on the rooster. If I double click one of them to start a conversation, the application crashes with SIGSEV, so I guess the account it's in fact disabled.

Starting Empathy with the account disabled, and enabling it, works perfectly.

Empathy 2.32.0.1, Fedora 14 beta.
Comment 1 Juan J. Martinez 2010-10-18 17:02:08 UTC
Sorry, I meant that the contacts "remain as online contacts" -- I have the option View > Offline Contacts unchecked.
Comment 2 Guillaume Desmottes 2010-10-19 09:23:45 UTC
What happen if you change your presence to offline? The contacts stay as well?
Which version of folks are you using?
Comment 3 Juan J. Martinez 2010-10-19 09:33:46 UTC
Changing to offline works, and I think it's because it affects all the accounts.

I have two different jabber accounts connected, with different contacts, and this happens when I disable one of them.

I don't know what version of folks I'm using (empathy 2.32.0.1). How do I check it?
Comment 4 Juan J. Martinez 2010-10-19 09:35:34 UTC
I'm sorry, I should have said that I have two accounts connected. Seems that's important to reproduce the bug.
Comment 5 Philip Withnall 2010-10-20 18:39:44 UTC
(In reply to comment #3)
> Changing to offline works, and I think it's because it affects all the
> accounts.
> 
> I have two different jabber accounts connected, with different contacts, and
> this happens when I disable one of them.

Could you run Empathy from the terminal with the following command and either attach the resulting log file here, or e-mail it to philip.withnall@collabora.co.uk please?

FOLKS_DEBUG=all empathy &> empathy.log

> I don't know what version of folks I'm using (empathy 2.32.0.1). How do I check
> it?

`yum info "*folks*"`
Comment 6 Juan J. Martinez 2010-10-20 18:57:07 UTC
OK, I didn't know it was a package:

$ yum list installed "*folks*"
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_GB to language list
Installed Packages
folks.x86_64                        0.1.16-1.fc14                        @fedora

I'll try to process the log you're asking for to protect my privacy and I'll send you it by mail.
Comment 7 Juan J. Martinez 2010-10-20 19:19:50 UTC
OK, I've sent the log anonymizing my contacts.
Comment 8 Philip Withnall 2010-10-23 12:17:41 UTC
Version 0.1.16 is quite old — this bug was fixed in 0.1.17. I hope Fedora updates its libfolks package to at least 0.2.0 before Fedora 14 is released.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 629082 ***
Comment 9 Brian Pepple 2010-11-14 22:09:46 UTC
(In reply to comment #8)
> Version 0.1.16 is quite old — this bug was fixed in 0.1.17. I hope Fedora
> updates its libfolks package to at least 0.2.0 before Fedora 14 is released.

Unfortunately, folks in Fedora can't be updated past 0.1.16 since all versions after that require a gobject-introspection > 0.9.3 (which is what F14 has). Talked to the desktop team about update go-i and they felt the pain involved in updating it wasn't worth it (due to the other components that use go-i).