Opened 10 years ago

Closed 10 years ago

#9467 closed defect (fixed)

Unknown Error 1013

Reported by: talonsofthestorm Owned by: marv
Milestone: 2.6.0 Component: Yahoo!/Yahoo! JAPAN
Version: 2.5.7 Keywords: Yahoo!, Error 1013
Cc:

Description

I upgraded pidgin to 2.5.7 today to attempt to get my yahoo client working as my AIM does. When I tried to enable the account for yahoo, pidgin gave me "unknown error 1013. Logging into the Yahoo! website may fix this." So, I logged into the site, tried again, and pidgin still gave me the unknown error 1013.

Attachments (1)

pidgin_error_debug (18.4 KB) - added by umattu 10 years ago.
Pidgin debug output

Download all attachments as: .zip

Change History (10)

comment:1 Changed 10 years ago by sulabh.dev

  • Status changed from new to pending

There is no error 1013 in y16 login method. This appears the case of webmessenger login. Why is webmessenger login being used in this user's case?

Run Pidgin with -d, and provide us the debug log generated.

comment:2 Changed 10 years ago by Porkrinds

I read over at Miranda about this bug (found via Google search) and it said to remove the @yahoo.com part from your login credentials. After doing this, I no longer received this error message and was able to login.

comment:3 follow-up: Changed 10 years ago by darkrain42

  • Status changed from pending to new

Ugh, Porkrinds is correct (at least, I can certainly reproduce error 1013 here).

Sulabh, how difficult would it be to strip off "@yahoo.com" of the username for authentication/setting the connection display_name?

Changed 10 years ago by umattu

Pidgin debug output

comment:4 Changed 10 years ago by umattu

I have attached the debug output for those who are interested. I can confirm that removing the "@yahoo.com" works. Thanks alot!!

comment:5 in reply to: ↑ 3 ; follow-up: Changed 10 years ago by sulabh.dev

Replying to darkrain42:

Ugh, Porkrinds is correct (at least, I can certainly reproduce error 1013 here).

I got confused by the webmessenger login thing. Anyways, I was able to reproduce it as well.

Sulabh, how difficult would it be to strip off "@yahoo.com" of the username for authentication/setting the connection display_name?

It is easy to do that, we can call purple_account_set_username(name) from yahoo prpl, where name would be after stripping off "@abc.xyz" (yahoo has several domains not just yahoo.com).

Yahoo username is the id not the email address. I think we should instead just check in our login procedure whether user is providing his id or email address, warn the user and disable the account in case email address is being provided.

I will do whatever other prpls do for such a case, how is such a thing handled in other prpls?

We shouldn't put an email address in the field for username in the first place :P

comment:6 in reply to: ↑ 5 ; follow-up: Changed 10 years ago by darkrain42

Replying to sulabh.dev:

It is easy to do that, we can call purple_account_set_username(name) from yahoo prpl, where name would be after stripping off "@abc.xyz" (yahoo has several domains not just yahoo.com).

Yahoo username is the id not the email address. I think we should instead just check in our login procedure whether user is providing his id or email address, warn the user and disable the account in case email address is being provided.

My understanding is that some Yahoo accounts *do* require the @domain part (in particular, things like @sbcglobal.net, etc). However, rekkanoryo corrected me last night in devel@cpi. Apparently, sometimes the "@yahoo.com" is necessary for a user to log in (his guess is if rekkanoryo@… and rekkanoryo@… both exist, one is required to use the full domain).

BigBrownChunx? suggested perhaps trying to append/strip "@yahoo.com" if the first authentication attempt failed. I don't know if that's possible or not.

I pretty strongly feel that, if it's possible for us to detect this, we should handle it, if at all possible, automatically.

comment:7 in reply to: ↑ 6 Changed 10 years ago by sulabh.dev

  • Milestone set to 2.6.0

Replying to darkrain42:

My understanding is that some Yahoo accounts *do* require the @domain part (in particular, things like @sbcglobal.net, etc). However, rekkanoryo corrected me last night in devel@cpi. Apparently, sometimes the "@yahoo.com" is necessary for a user to log in (his guess is if rekkanoryo@… and rekkanoryo@… both exist, one is required to use the full domain).

Things like @sbcglobal.net, yeah how can I forget them. Also as far as I know we cant have account both at @yahoo.com and say @yahoo.co.in.

BigBrownChunx? suggested perhaps trying to append/strip "@yahoo.com" if the first authentication attempt failed. I don't know if that's possible or not.

I pretty strongly feel that, if it's possible for us to detect this, we should handle it, if at all possible, automatically.

If error 1013 is KNOWN to occur ONLY when we have this discussed problem, then it can be dealt with. If there are other reasons error 1013 can occur, we would have a problem.

comment:8 Changed 10 years ago by umattu

I have always used the @yahoo.com when logging into Yahoo messenger using the yahoo client, pidgin, kopete, etc and have never had this issue. It certainly is easy enough to remove the domain from the username, but it would be nice if pidgin could handle this more gracefully.

comment:9 Changed 10 years ago by talonsofthestorm

  • Resolution set to fixed
  • Status changed from new to closed

I feel so silly, though I thought I remembered nixing the "@yahoo.com" at one point and it also not working. But I removed it, and now it works! Thank you all for your input!

And you are right, there should be a warning to not put the "@yahoo.com" in the username.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!