Bug 223665

Summary: kopete yahoo doesn't give error on failed authentication
Product: [Unmaintained] kopete Reporter: Philipp <philipp_foerster>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: colemichae, mpictor
Priority: NOR    
Version First Reported In: 0.80.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Philipp 2010-01-21 12:24:45 UTC 
Version:           0.80.2 (using KDE 4.3.4)
OS:                Linux
Installed from:    Ubuntu Packages

if a wrong yahoo user name or password is entered kopete won't connect, and won't display any error. this is very misleading. i thought the problem would be the protocol or a connection error.

the problem for me was that i entered my username like this xxxxxxx@yahoo.com instead of xxxxxxx. maybe kopete could automatically strip of the @yahoo.com or mention what exactly to enter into the field. something like "Yahoo User Name (without @yahoo.com)"

i think there are quite a few people who could not connect because of this. i didn't figure it out for months, i thought that kopete's yahoo protocol was broken.
Comment 1 Philipp 2010-01-21 12:27:43 UTC 
related thread:
http://forum.kde.org/viewtopic.php?f=18&t=62097
Comment 2 Michael Cole 2010-01-21 14:36:07 UTC 
This is a confirmed bug and has been fixed the Yahoo plugin was missing the reply and just trying over and over again.

This has now been fixed..
Comment 3 Philipp 2010-01-21 20:34:48 UTC 
nice ! thanks !
Comment 4 Mark 2011-09-20 22:10:55 UTC 
I have this same problem with a newer version of kopete!  If I use xxxx@yahoo.com, it simply says I'm offline - no error. Using xxxx works.

About box says:
Version 1.0.80
Using KDE Development Platform 4.6.4 (4.6.4)

Debian package manager says
Package: kopete (4:4.6.5-2)

package url: http://ftp.us.debian.org/debian/pool/main/k/kdenetwork/kopete_4.6.5-2_amd64.deb

64-bit debian testing

Can this bug be reopened/updated to a new version, or should I open a new bug?