Kopete cannot log into yahoo IM

I have read the manual and followed the instructions but I cannot get kopete to connect to yahoo.

Problem descriptions of only half a line length are seldom sufficient.

As long as you do not even tell which version of openSUSE, KDE, etc. this is about, you will make it more difficult for people to help you. I do not think you want to shy potential helpers away from your problem, don’t you?

And you should describe waht you do. “I have read the manual and followed the instructions” does not explain very much. Which manual, what instructions? In short, you better describe exactly what you do, what you expect to happen which each step and what happens instead.

ok, fair enough.

The manual I refer to is "
Introduction to Instant Messaging" located at Chapter

I entered my yahoo login name and password and I expected that Kopete would log in login and load up my contats but that didn’t happen…
I received the following error;
Unable to connect: Error resolving scsa.msg.yahoo.com:
Name or service not known

I tried to use pigeon with similar results so I suspect it is not the apps with the issues but perhaps yahoo AND kopet and pigeon all have issues

Kopete
Version 1.1.2
Using KDE Development Platform 4.7.2 (4.7.2) "release 5

OS: Linux 3.1.10-1.9-desktop x86_64
Current user: bilbo@linux-y8y3
System: openSUSE 12.1 (x86_64)
KDE: 4.7.2 (4.7.2) “release 5”
MD Phenom™ II X6 1090T Processo

When it says

 Error resolving scsa.msg.yahoo.com:

this means that your DNS server can not resolve that name to an IP address. Did you configure a DNS server, or did you get one from your DHCP server (most probably your router). (My system can resolve it, thus the spelling is correct).

Show us:

cat /etc/resolv.conf

bilbo@linux-y8y3:~> cat /etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!


On 06/21/12 12:46, coasterad pecked at the keyboard and wrote:
> Code:
> --------------------
>
> bilbo@linux-y8y3:~> cat /etc/resolv.conf
> ### /etc/resolv.conf file autogenerated by netconfig!
> #
> # Before you change this file manually, consider to define the
> # static DNS configuration using the following variables in the
> # /etc/sysconfig/network/config file:
> # NETCONFIG_DNS_STATIC_SEARCHLIST
> # NETCONFIG_DNS_STATIC_SERVERS
> # NETCONFIG_DNS_FORWARDER
> # or disable DNS configuration updates via netconfig by setting:
> # NETCONFIG_DNS_POLICY=’’
> #
> # See also the netconfig(8) manual page and other documentation.
> #
> # Note: Manual change of this file disables netconfig too, but
> # may get lost when this file contains comments or empty lines
> # only, the netconfig settings are same with settings in this
> # file and in case of a “netconfig update -f” call.
> #
> ### Please remove (at least) this line when you modify the file!
>
>
> --------------------
>
>
You don’t have any nameservers configured, add the following google
nameservers to the end of the file:

nameserver 8.8.8.8
nameserver 8.8.4.4

I am a total linux newb - how do I edit this file?

You can also use YaST for it: YaST > Network devices > Network settings and then the tab Hostname/DNS. Fil in Nameserver 1 and 2 with the IP addresses given. Or use those your ISP provides.

I had the file edited with vi but I couldn’t figure out how to save and exit it

ok, the file is edited but still no joy


linux-y8y3:/home/bilbo # cat /etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
nameserver 192.168.1.254
nameserver 8.8.8.8
nameserver 8.8.4.4


ok, new error for both kopete and pidgin
pidgin had an SSL error and kopete had the the following:.


KUniqueApplication: Cannot find the D-Bus session server:  "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." 

kopete(2275): KUniqueApplication: Pipe closed unexpectedly.

Could not log into the yahoo service error code 1013

In vi to go to the “command line” you use* :. Then you can type commands viewable in the last line of the screen.
It is the w command to write the file and the q command to quit. Thus, first :w, then
:q*.

That is not exactly what we said, It is either, or. Thus eithter you use your own router (which seems to work), or you use Google"s (which you now have as second and third as your router quits). But when your router quits, you can not go to the internet and thus to Google :).

I got it - thank all so much for the time you spent to help me.

There were two problems, the DNS issue which resolved after I edited the config file and my login name to yahoo - do not use @yahoo.com as part of your login name - lol

About your new errors, I caan not say much. Hope that people with knowledge about this subjject jump in here.
The DNS one was easy :wink: