Ubuntu
evolution package

Pidgin-Evolution integration flaky

Bug #235250 reported by J. Pablo Fernández
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evolution
Confirmed
Unknown
evolution (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

There's no way to specify which Pidgin-contact belongs to each Evolution-contact and after the synchronization, if you modify the Evolution-contact, a new one is created in a new synchronization.

Revision history for this message
Nick Ellery (nick.ellery) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in pidgin and evolution.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in pidgin:
status: New → Incomplete
Revision history for this message
J. Pablo Fernández (pupeno) wrote :

Yes, same behavior. Contact A is in Pidging, contact A is in Evolution configured with the corresponding jabber address. You synchronize contacts and you get another contact A in Evolution. Useless.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Thank you J. Pablo, so setting this back to confirmed. I found two related bugs in the gnome bug tracker, can you please check if they describe your problem appropriately?
http://bugzilla.gnome.org/show_bug.cgi?id=340390
http://bugzilla.gnome.org/show_bug.cgi?id=499584

Unfortunately it seems like there is not much being done about this. Thanks.

Changed in pidgin:
status: Incomplete → Confirmed
Revision history for this message
J. Pablo Fernández (pupeno) wrote :

Yes, those two seems related. The first one http://bugzilla.gnome.org/show_bug.cgi?id=340390 points to a field mismatch (icq vs aim), which I would say it's not the real problem since it happens to me using only jabber. The second one, http://bugzilla.gnome.org/show_bug.cgi?id=499584, is right on target. Even worst than not checking for current contact is the fact that the newly created contacts as soon as modified become unsynced and yet another contact is created.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Ok, so I linked the second one to the Evolution project. Thank you very much.

Changed in evolution:
importance: Undecided → Unknown
status: New → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
status: Unknown → New
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)
Changed in evolution:
importance: Undecided → Low
status: Confirmed → Triaged
Sebastien Bacher (seb128)
Changed in evolution (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
Revision history for this message
C de-Avillez (hggdh2) wrote :

Updated upstream tracker to base Gnome bug (499584 has been marked as a duplicate).

Changed in evolution:
status: New → Unknown
Revision history for this message
C de-Avillez (hggdh2) wrote :

Sigh. This bug is actually a duplicate of bug 157207... marking as such.

Bug Watch Updater (bug-watch-updater)
Changed in evolution:
status: Unknown → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.