Since last update of the KDE packages Kopete won’t connect to Yahoo! It works with Windows Live. I have version 0.70.4.
When I run it in terminal I get the following message:
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
kopete(6049)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '!
And when I try to connect:
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
kopete(6049): The kwalletd service has been disabled
Object::connect: No such signal ClientStream::disconnected()
Object::connect: (receiver name: 'yahooclient')
Transfer ACCEPTED by: LoginTask
Transfer ACCEPTED by: LoginTask
>
> Hello!
>
> Since last update of the KDE packages Kopete won’t connect to Yahoo! It
> works with Windows Live. I have version 0.70.4.
> When I run it in terminal I get the following message:
>
> Code:
> --------------------
>
> Calling appendChild() on a null node does nothing.
> Calling appendChild() on a null node does nothing.
> Calling appendChild() on a null node does nothing.
> kopete(6049)/libkopete Kopete::PluginManager::loadPluginInternal:
> Unable to find a plugin named ’ “” '!
> --------------------
>
> And when I try to connect:
>
> Code:
> --------------------
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> kopete(6049): The kwalletd service has been disabled
> Object::connect: No such signal ClientStream::disconnected()
> Object::connect: (receiver name: ‘yahooclient’)
> Transfer ACCEPTED by: LoginTask
> Transfer ACCEPTED by: LoginTask
> --------------------
>
>
> And here connecting hangs. Tried connecting with pidgin and connecting
> hangs. Tried it on my other computer running Ubuntu pidgin hangs there
> too. On a third computer running Windows, yahoo messenger connects. I
> can also connect on websites such as ‘Yahoo! Messenger for the Web’
> (http://webmessenger.yahoo.com) and ‘Meebo - Connecting AIM, MSN, Yahoo,
> Facebook, MySpace messengers’ (http://www.meebo.com)
>
> What could be the problem?
It’s a problem with 3rd party applications authenticating to Yahoo’s IM
servers. Yahoo is updating their servers, and as each server is
updated, Pidgin or any client that uses it’s libraries, like Adium will
fail to connect. Apparently Kopete is affected too. That’s why some
folks are having success with DNS tweaks and using specific IP
addresses to connect. It’s gonna be hit or miss with that, and
eventually that approach will fail as well, once all of the servers are
upgraded. So we’re waiting on patches…
the easiest way is probably to go to Webpin, search for the package there (“pidgin 2.5.7” – make sure that you choose the correct version of your operating system), and install it by clicking on the “install” button on the right.
Ok so the latest Kopete update fixes connection problems to Yahoo!(need confirmation) However it seems that file transfer from/to yahoo is broken. Is this happening to anyone else?
Well it’s working for me with the problems listed above. And I don’t remember having any connection tweaks. I don’t have “override default server information” ticked.