Bug 20452 - On my university, I am not able to connect to MSN (and KMess is)
Summary: On my university, I am not able to connect to MSN (and KMess is)
Status: RESOLVED DUPLICATE of bug 22508
Alias: None
Product: Telepathy
Classification: Unclassified
Component: butterfly (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-04 01:42 UTC by Ernst
Modified: 2010-02-18 04:07 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Ernst 2009-03-04 01:42:42 UTC
Hi,

I'm using Empathy 2.25.92, and before I used Empathy 2.24.1 on Ubuntu 8.10. As I want to connect to my MSN account, I installed telepathy-butterfly and added my account.
If I am at home, I can connect without problems.

However, if I am at my university, I can almost never connect to MSN (sometimes, I am connected for a while but most of the time I receive a network error). Of course, my university has some internet restrictions. However, with KMess I am able to establish a stable connection. So, I think there is a bug inside telepathy. (I filled it against butterfly, but I don't know if that's the correct package.)

I do encounter this bug also if I use haze to connect.

If you need more info (for example some connection tests), please ask me!

Thanks,
Ernst
Comment 1 Will Thompson 2009-03-04 02:10:17 UTC
Yeah, Butterfly is the right component (well, it should be against Butterfly and Haze, but Bugzilla doesn't let you have two components).

I can't speak for Butterfly, but as for Haze: try going into the Advanced pane of the account's properties in Empathy, and ticking Http Method. If that works, then we have yet another vote for either Haze or libpurple doing that fallback automatically.
Comment 2 Ernst 2009-03-04 02:18:08 UTC
Thanks for your help! However, I'm still receiving the 'netwerk error' for MSN with the 'http method' in Haze (with Butterfly uninstalled). So this is not a solution for me.
Bye bye,
Ernst
Comment 3 Will Thompson 2009-03-04 02:33:20 UTC
Could you fire up Pidgin, connect to MSN, and see what error it gives you (if any)?
Comment 4 Ernst 2009-03-04 02:43:25 UTC
I just installed pidgin 2.5.2 (from intrepids main repo). Using pidgin, I had to accept an unknown certificate from contacts.msn.com. After accepting, I was (stable, it seems) connected to MSN (thus without http method!)

As it just connects, I do not have an error log ;-).
Comment 5 Will Thompson 2009-03-04 03:59:32 UTC
I feared that you'd say that. :-)

I think the certificate warning should be gone with libpurple 2.5.4 or .5, and hence haze should start working with one of those...
Comment 6 Ernst 2009-03-04 04:08:27 UTC
Ok, thanks for your help!
As I do not know how to update to that libpurple / haze version, I will report back if it will work or not in the feature (when some of my repo's will have the updated version).

Still, this bug also exists in butterfly. Is this bug report enough to make the developers aware?
Comment 7 Ernst 2009-03-06 05:39:36 UTC
I want to confirm that, after installing the packages from http://www.getdeb.net/release/3960 (deb pidgin packages 2.5.5), msn haze is able to make a stable connection. Thanks for helping me!

(Hopefully, butterfly will also address this issue, but that is not really important as I have a work around (or will haze replace butterfly once?))
Comment 8 Olivier Le Thanh Duong 2010-02-01 10:44:38 UTC
Hi,
could you check if Kmess (and haze) connect via http? if yes this is a dup of #22508
Comment 9 Ernst 2010-02-02 07:44:22 UTC
Well, I just got my master, so I won't be at teh university soon, I guess. This means I cannot test anymore.
Comment 10 Olivier Le Thanh Duong 2010-02-18 04:07:49 UTC
I will mark it as a dup of #22508 then since there isn't much more we can do about it. Thanks for your report.

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


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.