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 630995 - Allow to remove personas from an individual
Allow to remove personas from an individual
Status: RESOLVED DUPLICATE of bug 629537
Product: empathy
Classification: Core
Component: Meta Contacts
2.32.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-09-30 11:14 UTC by skalka
Modified: 2010-09-30 12:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description skalka 2010-09-30 11:14:30 UTC 
It seems that linked contacts can be unlinked. If I push Unlink warning window appear but if I confirm my choice metacontact is still there, not unlinked.I'm on Ubuntu Maverick, Empathy 2.32.0.
Comment 1 Felix Kaser 2010-09-30 11:35:34 UTC 
did you link the contacts yourself or were they automatically linked? (maybe because they have the same jabber id, msn address, icq number, ...?)
Comment 2 skalka 2010-09-30 11:42:37 UTC 
Right question! Unlinking doesn't work only if link was automatic (same contact on two different jabber account). In this case splitting contacts will be useful to delete on of them, is it possible to do it in some way?
Comment 3 Felix Kaser 2010-09-30 11:52:30 UTC 
Splitting autolinked contacts is not possible right now. To delete one of the contacts is right now only possible by deactivating the other account, so the contact will be alone and not linked to the other contact.

But there should definitely be a way to remove one persona from an individual (in folks language ;) )
Comment 4 Philip Withnall 2010-09-30 12:02:16 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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