Gajim can't connect to GoogleTalk - nslookup: parse of /etc/resolv.conf failed

[Christoph Langner]

Binary package hint: gajim

I can't connect to my Google Talk account. I start with a clean profile, by deleting ~/.gajim and starting the program. I enter my data

<->
Username: <myname>
Server: gmail.com
Password: <secret>
<->

I finish the setup assistant and wait that gajim establishes the connection, but it fails with the message

<->
Can't connect to gmail.com
Check your connection or try later
<->

When i start gajim out of a terminal i see the following messages

<->
$ gajim
Requires docutils 0.4 for set_classes to be available
creating /home/user/.gajim directory
creating /home/user/.gajim/vcards directory
creating /home/user/.gajim/avatars directory
creating logs database
nslookup: parse of /etc/resolv.conf failed
<->

Here is my /etc/resolv.conf

<->
$ cat /etc/resolv.conf
#@VPNC_GENERATED@ -- this file is generated by vpnc
# and will be overwritten by vpnc
# as long as the above mark is intact
# Generated by NetworkManager
domain rz.uni-karlsruhe.de rz.uni-karlsruhe.de
search rz.uni-karlsruhe.de
nameserver 129.13.64.5
nameserver 129.13.96.2
<->

When i try the same thing under Hardy Heron from my computer at home it works...

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: gajim 0.11.4-0ubuntu2
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gajim
Uname: Linux 2.6.27-7-generic i686

[Nafallo Bjälevik (nafallo)]

This is not a bug in gajim.

[LaMont Jones (lamont)]

I can't reproduce the bug with nslookup here...

On a side note, search and domain directives overwrite one another. Either the first or last wins (don't remember or care which, it may well vary...), and determines the value(s) used for the other.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.