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 675969 - authentication failed for ICQ/AIM
authentication failed for ICQ/AIM
Status: RESOLVED NOTGNOME
Product: empathy
Classification: Core
Component: Accounts
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2012-05-13 10:11 UTC by Matthias
Modified: 2012-06-19 15:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
mission log file (586.51 KB, text/plain)
2012-05-13 10:11 UTC, Matthias
Details

Description Matthias 2012-05-13 10:11:10 UTC
Created attachment 213955 [details]
mission log file

Coinciding with an upgrade (ubuntu precise pangolin) I'm unable to connect to ICQ/AIM. In the account preferences the message is "Disconnected -- Authentication failed"

I attached debug output appearing when I try to enabled the account in the account preferences dialog.

I roughly checked the file. I found a message: 
"reason: 16 description: You have been connecting and disconnecting too frequently. Wait ten minutes and try again. If you continue to try, you will need to wait even longer."

But login on the website is possible without problems.

I found a forum entry suggesting to use pidgin (which I dislike) with modified settings: 
http://ubuntuforums.org/showthread.php?t=1944629

In the original setting it reports:
"""
You have been connecting and disconnecting too frequently. Wait ten minutes and try again. If you continue to try, you will need to wait even longer.
"""

When I disable the client login option as suggested in the forum I get:
"""
ACCOUNTNR disabled
Unknown reason
"""


Note that I already filed a downstream bug:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/993952
Comment 1 Guillaume Desmottes 2012-06-13 07:19:02 UTC
Let's see if setting the 'client-login' on your AIM account helps:

- Open a terminal
- Use 'mc-tool list' to find the name of your AIM accounts (something like 'haze/aim/test0')
- 'mc-tool  update haze/aim/test0 bool:use-clientlogin=1'

Replace the haze/aim/... with the name of your account of course.
Comment 2 Matthias 2012-06-13 11:32:11 UTC
Hi, 

thanks for the reply. I tried your suggestion. Unfortunately it does not change the situation. 

I checked with: 
mc-tool show haze/aim/MYACCOUNT

that the setting is set. The output contains the line: 
(bool) use-clientlogin = true

Please tell me if I should add any information or do any test. 

Regards, 
Matthias
Comment 3 Guillaume Desmottes 2012-06-13 13:47:59 UTC
Sorry I meant 
'mc-tool  update haze/aim/test0 bool:use-clientlogin=0'

Note that it doesn't connect in Pidgin without this option I doubt it will here. Did you find any wayt to connect using Pidgin?
Comment 4 Matthias 2012-06-13 14:50:58 UTC
Hi, 

It does not work with this setting as well. I also have not found a way to use pidgin. 

Currently I have to use meebo which works with the account :( 

Matthias
Comment 5 Guillaume Desmottes 2012-06-19 14:26:05 UTC
Right, so the first step would be to make it work with Pidgin (telepathy-haze uses the same library to connect as Piding). I suggest you to report this to Pidgin developers.
Comment 6 Matthias 2012-06-19 15:22:45 UTC
Hi, 

after additional research I found a fix (not to be confused with solution): 

- login.icq.com (instead of slogin.oscar.aol.com)
- disable encryption
- disabled client login

So the problem seems to be the combination
Comment 7 Matthias 2012-06-19 15:23:58 UTC
Hi, 

after additional research I found a fix (not to be confused with solution): 

- login.icq.com (instead of slogin.oscar.aol.com)
- disable encryption
- disabled client login

So the problem seems to be the combination of encryption and login server ... 

I will report to telepathy-haze