After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 586329 - Imported Google account (from Pidgin) not connecting
Imported Google account (from Pidgin) not connecting
Status: RESOLVED FIXED
Product: empathy
Classification: Core
Component: Accounts
2.27.x
Other All
: Normal normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2009-06-19 01:01 UTC by Asif Youssuff
Modified: 2009-06-20 11:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Asif Youssuff 2009-06-19 01:01:21 UTC
Please describe the problem:
Gtalk account imported from Pidgin using the account importer -- opening Empathy returns a jabber network error message.



I tried creating a new Gtalk account in empathy -- it connects without an issue.

Compared to the account auto imported from Pidgin, the account that empathy created when I selected google talk had these differences:

Server: talk.google.com
port: 5223

checked: ignore ssl certificate errors
checked: use old SSL

the account imported from pidgin has:

checked: encryption requried (TLS/SSL)
server: blank
port: 5222

If i add the server name (talk.google.com) to the imported gtalk account from pidgin, I am able to connect, with all other settings intact:

checked: encryption requried (TLS/SSL)
server: talk.google.com
port: 5222

Steps to reproduce:
1. Open Accounts dialog
2. Click import accounts
3. Select Google talk account
4. Try to connect


Actual results:
I get a jabber network error message.

Expected results:
Connected to Google account. 

Does this happen every time?
Yes. 

Other information:
Also tracked here: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/388522
Comment 1 Jonny Lamb 2009-06-19 08:09:41 UTC
Can you try again with empathy master please? This should be fixed as of commit 9c1dfe2afbea.
Comment 2 Jonny Lamb 2009-06-20 11:08:58 UTC
Marking as fixed. Feel free to re-open if you disagree after testing with master.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.