"Network Error" on any new Google Talk account

Bug #477233 reported by Tres Finocchiaro
90
This bug affects 25 people
Affects Status Importance Assigned to Milestone
Empathy
Fix Released
Medium
empathy (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: empathy

Fresh install Ubuntu 9.10 karmic AMD64 from Windows installer (Windows 7)
How to reproduce: Open Empathy, Add Gmail account, receive error "Network error"
Cause: "Server" field is blank in account preferences --> advanced. Value should be "talk.google.com"
Resolution: Manually type "talk.google.com" in server field and save account preferences.

ProblemType: Bug
Architecture: amd64
Date: Sat Nov 7 03:30:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: empathy 2.28.1-1ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: empathy
Uname: Linux 2.6.31-14-generic x86_64

Related branches

Revision history for this message
Tres Finocchiaro (tres-finocchiaro) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in empathy (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
Revision history for this message
Tres Finocchiaro (tres-finocchiaro) wrote :

Bug created through bugzilla.

https://bugzilla.gnome.org/show_bug.cgi?id=601089

-Tres

Changed in empathy (Ubuntu):
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package empathy - 2.29.91.2-0ubuntu1

---------------
empathy (2.29.91.2-0ubuntu1) lucid; urgency=low

  * new upstream release
    - URL in contact's status are not clickable (LP: #411150)
    - "Network Error" on any new Google Talk account (LP: #477233)
  * debian/patches/20_libindicate.patch
    - Updated for 2.29.91.2
  * debian/empathy.gconf-defaults
    - enable notifications when chat is not focused (LP: #460286)
 -- Ken VanDine <email address hidden> Thu, 04 Mar 2010 21:49:39 -0500

Changed in empathy (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Snahrck (hansenclever) wrote :
Download full text (7.4 KiB)

I'm using
Empathy 2.30.1
Lucid 10.04

I have this problem yet no matter what configuration I try.
Just to see if there was a firewall or something like that blocking my connection I tried the google's gtalk running under virtual box and it connects just fine on this machine.

Here I paste some gabber logs:

Default options (just created Google Talk account)
[CODE]
tp-glib-DEBUG: 19-05-2010 13:32:13.542414: started version 0.8.12 (telepathy-glib version 0.10.1)
gabble/connection-DEBUG: 19-05-2010 13:32:13.543111: gabble_connection_class_init: Initializing (GabbleConnectionClass *)0x8dbb4c0
gabble/connection-DEBUG: 19-05-2010 13:32:13.543287: gabble_connection_init: Initializing (GabbleConnection *)0x8dc1008
gabble/muc-DEBUG: 19-05-2010 13:32:13.543783: gabble_roomlist_manager_constructed: 0x8db35b8
gabble/connection-DEBUG: 19-05-2010 13:32:13.544971: gabble_connection_constructor: Post-construction: (GabbleConnection *)0x8dc1008
gabble/jid-DEBUG: 19-05-2010 13:32:13.545206: gabble_signal_connect_weak: connecting to 0x8db57c0:item-found with context 0x8db0380
gabble/jid-DEBUG: 19-05-2010 13:32:13.545213: gabble_signal_connect_weak: connecting to 0x8dc1008:status-changed with context 0x8db0400
gabble/connection-DEBUG: 19-05-2010 13:32:13.545296: gabble_connection_constructed: defaulted resource to ecc58192
gabble/connection-DEBUG: 19-05-2010 13:32:13.552211: _gabble_connection_connect: disabling SRV because "server" or "old-ssl" was specified or port was not 5222, will connect to talk.google.com
gabble/connection-DEBUG: 19-05-2010 13:32:13.552782: do_connect: calling lm_connection_open
LM-DEBUG: 19-05-2010 13:32:13.553133: Connecting to: talk.google.com:5222
LM-DEBUG: 19-05-2010 13:32:13.553406: SRV lookup disabled for talk.google.com
LM-DEBUG: 19-05-2010 13:32:13.553669: Going to connect to talk.google.com:5222
gabble/roster-DEBUG: 19-05-2010 13:32:13.554286: connection_status_changed_cb: adding callbacks
gabble/im-DEBUG: 19-05-2010 13:32:13.554615: connection_status_changed_cb: adding callbacks
gabble/muc-DEBUG: 19-05-2010 13:32:13.554892: connection_status_changed_cb: adding callbacks
LM-DEBUG: 19-05-2010 13:32:23.603220: Trying 74.125.65.125 port 5222...
LM-DEBUG: 19-05-2010 13:32:44.602807: Connection failed.
LM-DEBUG: 19-05-2010 13:32:44.602960: Connection failed: Connection timed out (error 110)
[/CODE]

All checkboxes marked
server: talk.google.com
port: 5223
[CODE]
tp-glib-DEBUG: 19-05-2010 13:29:46.484771: started version 0.8.12 (telepathy-glib version 0.10.1)
gabble/connection-DEBUG: 19-05-2010 13:29:46.485407: gabble_connection_class_init: Initializing (GabbleConnectionClass *)0x82c1d68
gabble/connection-DEBUG: 19-05-2010 13:29:46.485579: gabble_connection_init: Initializing (GabbleConnection *)0x82c8008
gabble/muc-DEBUG: 19-05-2010 13:29:46.485860: gabble_roomlist_manager_constructed: 0x82ba5b8
gabble/connection-DEBUG: 19-05-2010 13:29:46.486136: gabble_connection_constructor: Post-construction: (GabbleConnection *)0x82c8008
gabble/jid-DEBUG: 19-05-2010 13:29:46.486351: gabble_signal_connect_weak: connecting to 0x82bc7c0:item-found with context 0x82b7380
gabble/jid-DEBUG: 19-05-2010 13:29:46.486358: gabble_signal_connect_weak: conne...

Read more...

Changed in empathy:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Dylan McCall (dylanmccall) wrote :

I'm seeing this again in Maverick, and solved it with the workaround above. Can anyone confirm that?

Revision history for this message
Laurent Dinclaux (dreadlox) wrote :

I have the issue too in Maverick and adding talk.google.com is already filled for the failing accounts.

Revision history for this message
Jonas Alves (jonasfa) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.