Bug 683631 – Can't Connect to MSN

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 683631 - Can't Connect to MSN


Summary:	Can't Connect to MSN


Status:	RESOLVED INCOMPLETE

Product:	empathy
Classification:	Core
Component:	Accounts
Version:	3.3.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	empathy-maint
QA Contact:	empathy-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-09-08 17:15 UTC by Bilal Shahid
Modified:	2012-12-30 15:52 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
debug log (43.07 KB, text/plain) 2012-09-08 17:15 UTC, Bilal Shahid	Details

Description Bilal Shahid 2012-09-08 17:15:24 UTC

Originally reported at:
  https://bugs.launchpad.net/bugs/964339

I cannot connect to MSN. My password has not changed in the past several months and re-entering it in Online Accounts works but empathy can't connect.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.92-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Sat Mar 24 22:17:56 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: empathy
UpgradeStatus: Upgraded to precise on 2012-01-28 (56 days ago)

Comment 1 Bilal Shahid 2012-09-08 17:15:58 UTC

Created attachment 223816 [details]
debug log

Comment 2 André Klapper 2012-09-10 09:32:08 UTC

Please upgrade to a recent version first (stable 3.4 series or unstable 3.5 series) - 3.3.92 is an old unstable development version.

Comment 3 André Klapper 2012-12-30 15:52:21 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for in comment 2. Thanks!