When adding a Pidgin buddy from Evolution contacts wrong protocol type is used

Bug #282589 reported by clovepower
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: pidgin

pidgin 1:2.4.1-1ubuntu2.1

Ubuntu 8.04.1 AMD64 Linux set 2.6.24-19-generic

I've several accounts in Pidgin with different protocols. When I add a new buddy by choosing

Buddies > Add Buddies

it brings up an "Add Buddy" dialog that gives me the option to browse one of my Evolution address books for a buddy. The dialog however does not let me choose which Pidgin protocol should be used to add the buddy and it does not appear to be able to detect it properly. In my case, I choose a contact which has a only one MSN account specified (and as such is shown in "Add Buddy" dialog) but he's added as a new AIM buddy.

If in the "Add Buddy" dialog you click "New Person", the "New Person" dialog correctly contains an "Account type" field to choose account type.

1. Open Evolution
2. Add a new contact, enter a valid MSN address under Instant Messaging (and only that)
3. Open Pidgin, make sure you have accounts under different protocols (AIM and MSN in my case)
4. Choose Buddies > Add Buddies and choose the newly added Evolution contact

The buddy is not added to Pidgin with MSN protocol (it uses AIM in my case)
Protocol type should be automatically be MSN, or an option to specify a protocol type should be given

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

Changed in pidgin:
status: New → Incomplete
Revision history for this message
clovepower (mzattera) wrote :

The computer I'm using is used for production, so it runs LTS distributions only.

Beside, I would like to see this issue fixed in 8.04, since this is supposed to be still supported.

That said, I can do the test if you say it's possible using the live CD.

Revision history for this message
BigBadBassMan (d-reiche) wrote :

This applies to 8.10 as well, no matter of the pidgin version being used. (tried 2.5.2 from repo, and 2.5.5 from getdeb.net)

Additionally: Pidgin does add ICQ-Buddies to AIM-Accounts without problem,or notice - everything works here. Protocolls seem to be compatible. However, adding a ICQ contact to MSN does not work, as "@hotmail.com" is automatically appended to the ICQ-UIN and the MSN-Server sends an error message.

I've added severall contacts to an AIM account, when I was supposed to add them to ICQ, and did not notice it. Only beeing told by my contacts that I was not displayed with the ICQ-standard protocol symbol "flower" lead me to this discovery.

This is annoying, as i cannot re-apply for Authentication on buddies present within AIM _and_ ICQ. So I'm forced to use AIM, because I cannot use them with ICQ.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue in jaunty? to be sent to pidgin.im by somebody having the bug

Changed in pidgin (Ubuntu):
importance: Undecided → Low
Revision history for this message
lewvip (lewvip-163) wrote :

yes, it also puzzled me a lot.
so I disabled the plugin of evolution integration, "add buddy" works fine

Revision history for this message
BigBadBassMan (d-reiche) wrote :

seems to be fixed within lucid..

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pidgin (Ubuntu) because there has been no activity for 60 days.]

Changed in pidgin (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Rolf Leggewie (r0lf) wrote :

no, lucid is still affected. Reopening.

Changed in pidgin (Ubuntu):
status: Expired → Triaged
Revision history for this message
Rolf Leggewie (r0lf) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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