Can't connect to msn accounts

Hi,

It's a known problem in pymsn, I will as a sync as soon as a fixed package hits debian

and of course making SRU packages to fix the bug in previous version of ubuntu

needs ack from motu-sru, and should be fixed in intrepid first.

0.3.3-0ubuntu1 uploaded in intrepid

ping?

ACK from MOTU-SRU as long as Laurent promises to keep a close eye on the package after the SRU. :]

Accepted into -proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

With the proposed update, connects ok now here (Hardy)

Works here too. Hardy 64 bit

I can also report that the proposed update fixed the problem for me. Could not connect to msn using empathy before, and now I can! Running Hardy 32-bit.

Thanks guys,
James.

Copied to hardy-updates.

Hi,
I'm getting this exact same problem in Intrepid Beta. Has the fix been added to the Intrepid repo as well?

Thanks
Matt

looks like it can be resolved by killing telepathy-butterfly, then forcing a re-connect by going offline and back on again.

Hope this helps

This solution works for me too. It's inconvenient, but it's a work around. killall telepathy-butterfly, then hit "Availble" again

It still appear now in Intrepid. Killing telepathy-butterfly and re-connecting does not work for me.

Killing telepathy-butterfly works here! Thanks =)

I just had the same bug on Jaunty Beta. Killing telepathy-butterfly did fix it.

This is still happening in Jaunty final release, using Empathy 2.27.1.1 (from the Telepathy Team PPA: http://ppa.launchpad.net/telepathy/ppa/ubuntu). Killing telepathy-butterfly fixes this problem for me, but you have to do this every time you start empathy.

Yeah, this bug is still present in Jaunty. Using the Emapthy version that's in the official Ubuntu repos it first doesn't connect to the MSN network. Killing "telepathy-butterfly" fixes the problem here too. But doing this everytime you start Empathy is kind of annoying...

Confirmed this is still an issue in Jaunty

telepathy-butterfly 0.3.3-1
python-msn 0.3.3-0ubuntu3

got the same problem in jaunty with empathy 2.27, any progress on a fix?

Have you tried to install latest version of telephathy-butterfly from ppa?, Anyway you would attach your empathy log file for looking more details about your problem.

Regards

My issue is more strange: I have 2 accounts: One with @hotmail and another with custom email. My account with custom email got looged in, but the @hotmail return a Network Error like this bug report says. Using karmic alpha updated 3 hours ago.

If some debug is needed, please tell-me

Debug anyway. Frist connection attempt was made using my hotmail.com account. Seccond was done (and sucessfully with my custom mail account):

(empathy:6149): empathy-DEBUG: accounts_dialog_enable_toggled_cb: Enable account leleobhzdiscovery
(empathy:6149): empathy-DEBUG: account_status_changed_cb: Status of account msn0 became status: 1 presence: 0 reason: 1
(empathy:6149): empathy-DEBUG: enable_or_disable_account: Account leleobhzdiscovery is now enabled
(empathy:6149): empathy-DEBUG: account_status_changed_cb: Status of account msn0 became status: 2 presence: 0 reason: 2
(empathy:6149): empathy-DEBUG: account_status_changed_cb: Status of account msn0 became status: 1 presence: 0 reason: 1
(empathy:6149): empathy-DEBUG: account_status_changed_cb: Status of account msn0 became status: 2 presence: 0 reason: 2
(empathy:6149): empathy-DEBUG: account_status_changed_cb: Status of account msn0 became status: 1 presence: 0 reason: 1
(empathy:6149): empathy-DEBUG: accounts_dialog_enable_toggled_cb: Disabled account leleobhzdiscovery
(empathy:6149): empathy-DEBUG: account_status_changed_cb: Status of account msn0 became status: 2 presence: 0 reason: 1
(empathy:6149): empathy-DEBUG: enable_or_disable_account: Account leleobhzdiscovery is now disabled
(empathy:6149): empathy-DEBUG: builder_get_file_valist: Loading file /usr/share/empathy/empathy-account-widget-jabber.ui
** (empathy:6149): DEBUG: mc_account_get_param_string: Password found in keyring
** (empathy:6149): DEBUG: mc_account_get_param_string: Password found in keyring
(empathy:6149): empathy-DEBUG: account_widget_entry_focus_cb: Setting account to <email address hidden>
(empathy:6149): empathy-DEBUG: accounts_dialog_add_or_update_account: Adding new account
(empathy:6149): empathy-DEBUG: builder_get_file_valist: Loading file /usr/share/empathy/empathy-account-widget-msn.ui
** (empathy:6149): DEBUG: mc_account_get_param_string: Password found in keyring
** (empathy:6149): DEBUG: mc_account_get_param_string: Password found in keyring
(empathy:6149): empathy-DEBUG: account_widget_entry_focus_cb: Setting account to <email address hidden>
(empathy:6149): empathy-DEBUG: account_widget_entry_focus_cb: Setting password to ***
** (empathy:6149): DEBUG: mc_account_set_param_string: Storing password in keyring
(empathy:6149): empathy-DEBUG: account_widget_entry_focus_cb: Setting account to <email address hidden>
(empathy:6149): empathy-DEBUG: account_widget_entry_focus_cb: Setting password to ***
** (empathy:6149): DEBUG: mc_account_set_param_string: Storing password in keyring
(empathy:6149): empathy-DEBUG: accounts_dialog_name_editing_started_cb: Editing account name started; stopping flashing
(empathy:6149): empathy-DEBUG: accounts_dialog_enable_toggled_cb: Enable account <email address hidden>
(empathy:6149): empathy-DEBUG: account_status_changed_cb: Status of account msn1 became status: 1 presence: 0 reason: 1
(empathy:6149): empathy-DEBUG: enable_or_disable_account: Account <email address hidden> is now enabled
(empathy:6149): empathy-DEBUG: account_status_changed_cb: Status of account msn1 became status: 0 presence: 0 reason: 1
(empathy:6149): empathy-DEBUG: account_status...

Problem persists for me with latest karmic alpha-4.

Correction from my side: I can connect to MSN accounts now. It did not work yesterday shortly after I installed karmic on my computer. Today, everything works! Don't know why.

I remember that one problem yesterday was that empathy sometimes forgets the handle/username for MSN accounts. I.e., I can enter it as often as I want, it keeps forgetting that handle and as a result I cannot checkmark the MSN account.

Have also had this problem in Karmic, with "Network Error" as the error message.

On that note, it's apparent in Jaunty still. What's more - when I added my new MSN account with only 3 contacts, it connected fine on both distributions; my main MSN account has 400+ contacts on.

Ubuntu Karmic still need to be fixed

Just started to see problems with this on Karmic. It was working yesterday, but today it will not connect. I don't see any error messages or anything.

Happy to provide logs if needed.

also having same problems in karmic.

it would be good if one person having the problem could type "apport-collect 255307: in their terminal. This will give us up to date computer information, also if you could provide a backtrace using https://wiki.ubuntu.com/Backtrace for instructions on how.

This just happened to me on Ubuntu Karmic using Empathy 2.28.1.1. As a workaround;
1/ quit empathy via Chat > Quit
2/ In a terminal to find and the butterfly task via "sudo ps -A | grep telepathy-butte" then kill it via "sudo kill nnnn" where nnnn is the task number
3/ Restart empathy via Applications > Internet > Empathy IM Client
Now connects to MSN ok.

Empathy 2.28.1.1 doesn't seem to call telepathy-butterfly anymore.
I have the same problem, but there is no telepathy process to kill, and msn NEVER works for any of my msn accounts on two of three of my Karmic machines.

I have not found a work around that results in MSN connecting.

Can't get telepathy-butterfly to work either, it works wite Haze. I'm also using an non @hotmail or @live account.

OS: Ubuntu 9.10 x64.

I am having the same issue with Empathy and MSN.

This is a major issue, since MSN is one of the largest (I think the largest) IM network, and Empathy is the default client. I think this can be a bad first impression for new Ubuntu users.

Needs to be fixed now, or the default IM client should be changed to another client, like Pidgin.

I found this solution:

http://ubuntu-utah.ubuntuforums.org/showpost.php?p=8058121&postcount=9

that is,

"ok try this remove telepathy-butterfly an you should just have telepathy-haze installed try connecting with that".

and it just works!

There must be a conflict between the two libraries. I think this can be provided as a fix in Ubuntu updates soon.

Well telepathy-butterfly and telepathy-haze shouldn't conflict each other.

It's true that tp-haze provides an other implementation of msn protocol, but it also provides other protocols. So some people want to have both installed at the same time.

It's a choice in empathy to use tp-butterfly implementation instead of tp-haze one when booth are installed

Do you mean a choice when it is compiled, or somewhere else?

Well it a choice made by the developers

I tested the solution posted in reply #39..it seems to work so far.
Notice that :
- I had to reboot to make empathy "detect its new envoronment"
- the msn account was gone, I added it and it worked instantly.
- past conversations are not visible anymore. They are still present though in /home/<user>/.local/share/Empathy/logs.

cheers

Removing telepathy-butterfly worked for me too...

OK removing telepathy-butterfly did work but for some reason this caused cups not to start during boot which resulted in printer issues. So if anyone has the same problem just reinstall cups (sudo apt-get install --reinstall cups) and you should be fine.

Ok, I'm having as similar issue as above. I'm using an @hotmail address. when I run #ps -e I only have:

 1879 ? 00:00:00 telepathy-haze
 1881 ? 00:00:01 telepathy-gabbl

should I kill telepathy-haze?

I don't have telepathy-butterfly so post #39 will not work for me.

Thanks in advance!

This seems to affect Lucid and Maverick as well. Pidgin has no trouble connecting.

I am seeing segaults in telepathy-haze when tryig to use Empathy as well (found in kern.log). Happy to provide logs files if people tell me where Empathy is hiding them!

the bug is fixed in lucid and maverick. please update.

This is absolutely *not* fixed in Lucid or Maverick. This screenshot is friom a Lucid system, it's the same on my Maverick boxes and virtual images.

If someone can tell me where the Empathy logs lie, I a am happy to provide them.

Contrary to what I just said, if you refresh the repos you should see an update for "python-papyon" (0.4.8.-0ubuntu2). That seems to fix the problem - Empathy now connects to MSN.

Temporary Fix for the recent issue: http://andregondim.eti.br/?p=2364

Translating:

From file /usr/share/pyshared/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py - Change

CONTACTS = (“contacts.msn.com“,”?fs=1&id=24000&kv=7&rn=93S9SWWw&tw=0&ver=2.1.6000.1″)

|
|
v

CONTACTS = (“contacts.msn.com“, “MBI”)

Answering #49, The bug was now fixed with last update.

root@ana:~# LANG=C aptitude show python-papyon ; LANG=C aptitude download python-papyon
Package: python-papyon
State: installed
Automatically installed: no
Version: 0.5.1-0ubuntu2
Priority: optional
Section: python
Maintainer: Devid Antonio Filoni <email address hidden>
Uncompressed Size: 1638k
Depends: python (>= 2.5), python-support (>= 0.90.0), python-gobject (>= 2.10), python-openssl (>= 0.6), python-gst0.10, python-farsight, python-crypto
Provides: python2.6-papyon
Description: MSN client library written in Python
 papyon is an MSN client library, that tries to abstract the MSN protocol gory details. It is a fork of the unmaintained pymsn MSN library. papyon uses the GLib main
 event loop to process the network events in an asynchronous manner.
Homepage: http://www.freedesktop.org/wiki/Software/papyon

Get:1 http://sft.if.usp.br/ubuntu/ maverick-updates/main python-papyon all 0.5.1-0ubuntu2 [177kB]

Please this is an old bug opened in 2008, this has nothing to do with recent MSN issue with empathy/telepathy-butterfly/papyon

The right bug is bug 663670

Closing the jaunty task as jaunty is past EOL

karmic has seen the end of its life and is no longer receiving any updates. Marking the karmic task for this ticket as "Won't Fix".