error message while trying to use my MSN account in bitlbee

[Vicente Herrera Cobo]

PROBLEM

Unable to login to MSN via bitlbee

TEST CASE

(Need to have a live/msn messenger account with associated <email address hidden>)
1. ~$ sudo aptitude install irssi bitlbee
(Make sure bitlbee local server is running)
2. ~$ irssi
(In irssi)
3. /connect localhost
(in bitlbee window)
4. account add msn <email address hidden> password
5. account on
* Fails to login with "Error during Passport authentication: Could not parse Passport server response"

ORIGINAL

Ubuntu 9.10 - Karmic Koala. Bitlbee version 1.2.4-1
Also affects distribution Trisquel GNU/Linux 3.5 - http://trisquel.info/

From bitlbee web page:

"If you're getting the following error message while trying to use your MSN account:

Error during Passport authentication: Could not parse Passport server response

This is caused by BitlBee being a little bit too restrictive in the responses it gets from the authentication server. This bug is fixed in bzr and this code is live on im.bitlbee.org and testing.bitlbee.org. A fix will most likely come out as a version 1.2.7 very soon. "

http://bugs.bitlbee.org/bitlbee/changeset/devel%2C578

"BitlBee 1.2.7 was just released with the fix for the MSN Messenger login issues.

It includes some other changes (mostly IM module fixes and a show_offline setting that lets you have your offline contacts in the control channel as well."

[Martin Erik Werner (arand)]

If anyone is interested, I just packaged this for karmic in my ppa: https://edge.launchpad.net/~arand/+archive/ppa and it seems to work ok.

The updated version is in debian currently, so likely it will be pulled down for Maverick.

In the meantime, if we want to get this fixed officially in earlier versions, we'll have to get a small diff in order for a SRU.

[Martin Erik Werner (arand)]

I can confirm that the SVN fix works. I intend to get some packages for SRU ready in the near future. Four affected releases presumably, oh joy....

[Martin Erik Werner (arand)]

DEP-3 patch from SVN commit

[Martin Erik Werner (arand)]

On second check, nope, above patch does not fix the issue.

[Martin Erik Werner (arand)]

On third check, blargh that was just a failed attempt to package the patch.

Patch IS ok.

[Rey Tucker (rtucker)]

This bug also impacts hardy; my dpkg-fu is weak, but if someone can roll a .deb with the patch, I can test it on a hardy system.

[Martin Erik Werner (arand)]

Yea, I'm preparing debdiffs for dapper(?) to lucid, provided the patch applies correctly and no other older bugs with msn-bitlbee crops up.

[Martin Erik Werner (arand)]

debdiff for hardy

[Martin Erik Werner (arand)]

debdiff for jaunty

[Martin Erik Werner (arand)]

debdiff for karmic

[Martin Erik Werner (arand)]

debdiff for lucid

[Martin Erik Werner (arand)]

I'll check up on dapper later, subscribing sponsors and SRU team for now.

1.2.7 seems to have failed to build on Maverick, but as soon as it is fixed it should be open for a SRU.

Packages for testing on hardy-lucid are available for immediate testing from my "Main" PPA: https://edge.launchpad.net/~arand/+archive/ppa

[Rey Tucker (rtucker)]

The debdiff for hardy did the trick. Thank you!

[Chris Coulson (chrisccoulson)]

This is fixed in maverick already

[Martin Erik Werner (arand)]

Actually, it isn't fixed in maverick yet, since the Auto-sync from debian failed to build: https://edge.launchpad.net/ubuntu/+source/bitlbee/1.2.7-1
Rearranging assignments though, since I'm not involved in the maverick bit of things.

[Martin Erik Werner (arand)]

Resorted to vmware in order to get dapper running.
And for some strange reason, it works completely fine on current dapper version 1.0.1-1, hence marking that task as invalid.

[Martin Erik Werner (arand)]

Okay, now at least the i386, amd46 and armel are done, I'll take that as enough to call it released in maverick

[Martin Erik Werner (arand)]

Unassigning myself as per sponsorship policy

[Iain Lane (laney)]

All SRU diffs uploaded and waiting in unapproved for SRU team approval, thanks for your work!

[Martin Erik Werner (arand)]

Hrm, seems like I missed update-maintainer on the lucid version, that one could use a re-upload I'm afraid, here's the, hopefully correct, debdiff.

[Martin Pitt (pitti)]

Accepted bitlbee into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Martin Pitt (pitti)]

Accepted bitlbee into hardy-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Martin Pitt (pitti)]

Accepted bitlbee into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Martin Pitt (pitti)]

Accepted bitlbee into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Tony Whitmore (tonywhitmore)]

I've just installed this package on Lucid and MSN now seems to work fine,

[Launchpad Janitor (janitor)]

This bug was fixed in the package bitlbee - 1.2.4-2ubuntu0.1

---------------
bitlbee (1.2.4-2ubuntu0.1) lucid-proposed; urgency=low

  * Fix MSN Messenger login issues (LP: #581331)
    - BitlBee SVN fix by Wilmer van der Gaast
 -- Arand Nash <email address hidden> Thu, 20 May 2010 21:32:54 +0100

[Martin Pitt (pitti)]

Switching back to v-needed for hardy/jaunty/karmic.

[Martin Pitt (pitti)]

Anyone who can test this update on hardy, jaunty, and karmic?

[Rey Tucker (rtucker)]

I can verify that the MSN issue was fixed in 1.2-3ubuntu0.1 on hardy, and it has been running for a good while now without issue.

[Martin Pitt (pitti)]

Thanks Ryan! Moving hardy to -updates.

[Launchpad Janitor (janitor)]

This bug was fixed in the package bitlbee - 1.2-3ubuntu0.1

---------------
bitlbee (1.2-3ubuntu0.1) hardy-proposed; urgency=low

  * Fix MSN Messenger login issues (LP: #581331)
    - SVN fix by Wilmer van deer Gaast
 -- Arand Nash <email address hidden> Thu, 20 May 2010 21:19:45 +0200

[Jean-Baptiste Lallement (jibel)]

SRU verification for Karmic:
I have reproduced the problem with bitlbee 1.2.4-1 in karmic and have verified that the version of bitlbee 1.2.4-1ubuntu0.1 in -proposed fixes the issue.

[Jean-Baptiste Lallement (jibel)]

SRU verification for Jaunty:
I have reproduced the problem with bitlbee 1.2.3-1 in jaunty and have verified that the version of bitlbee 1.2.3-1ubuntu0.1 in -proposed fixes the issue. I've verified that I'm able to chat with myself.

Marking as verification-done

[Launchpad Janitor (janitor)]

This bug was fixed in the package bitlbee - 1.2.3-1ubuntu0.1

---------------
bitlbee (1.2.3-1ubuntu0.1) jaunty-proposed; urgency=low

  * Fix MSN Messenger login issues (LP: #581331)
    - BitlBee SVN fix by Wilmer van deer Gaast
 -- Arand Nash <email address hidden> Thu, 20 May 2010 21:55:59 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package bitlbee - 1.2.4-1ubuntu0.1

---------------
bitlbee (1.2.4-1ubuntu0.1) karmic-proposed; urgency=low

  * Fix MSN Messenger login issues (LP: #581331)
    - BitlBee SVN fix by Wilmer van der Gaast
 -- Arand Nash <email address hidden> Thu, 20 May 2010 19:04:19 +0100