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 586337 - Can't remove contact (Jabber)
Can't remove contact (Jabber)
Status: RESOLVED DUPLICATE of bug 599353
Product: empathy
Classification: Core
Component: Contact List
2.26.x
Other All
: Normal major
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2009-06-19 05:24 UTC by Henrique C. Alves
Modified: 2009-10-26 13:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Henrique C. Alves 2009-06-19 05:24:04 UTC 
Please describe the problem:
You can't remove yourself from the contact list. Tested this with a Jabber account, not sure if it happens on other accounts, might be interesting to check.

Steps to reproduce:
1. Add yourself as a contact (at least to a Jabber account)
2. Right-click the contact and select "Remove"


Actual results:
The contact still shows on the list.

Expected results:
Correctly remove it.

Does this happen every time?
Yes.

Other information:
Comment 1 Nicolò Chieffo 2009-07-09 13:14:42 UTC 
I suspect this problem happens also with other connection managers: and if you close + open empaty again you will not see the contact anymore (so the contact is actually removed from the account, but empathy still shows it)

Can you try what I'm suggesting?
Comment 2 Nicolò Chieffo 2009-07-09 13:28:04 UTC 
(this happens to me with 2.27.4 master, but I don't have the permission to change the version)
Comment 3 Louis-Francis Ratté-Boulianne 2009-07-25 23:22:52 UTC 
I think this commit fixed that (http://git.gnome.org/cgit/empathy/commit/?id=66f198c160fd6a8c1f3cce1a5e6237aeb1b20c99)
Comment 4 Sumana Harihareswara 2009-10-25 13:42:29 UTC 
I suspect this is a duplicate of bug #599353
Comment 5 Sumana Harihareswara 2009-10-26 13:20:49 UTC 

*** This bug has been marked as a duplicate of bug 599353 ***