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 579992 - Import of XMPP accounts sets port
Import of XMPP accounts sets port
Status: RESOLVED FIXED
Product: empathy
Classification: Core
Component: Preferences
2.26.x
Other All
: Normal normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2009-04-23 17:21 UTC by Tollef Fog Heen
Modified: 2009-06-05 14:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Tollef Fog Heen 2009-04-23 17:21:51 UTC 
Please describe the problem:
empathy imported my pidgin account automatically, but gave me "network error" when trying to connect.  With a bit of help, I tracked this down to gabble not doing SRV lookups when port is set.  I see in my pidgin preferences that port is set to 5222, but host is blank.  I saw the same in empathy's preferences, but there was no way for me to clear the port field.  Setting it to "0" or just blanking it would reset it to 5222.

Steps to reproduce:
1. create jabber account in pidgin, on server that's reachable via SRV records
2. start empathy, import account
3. see if fail to connect


Actual results:
It fails to connect due to not doing SRV lookups

Expected results:
It would connect and I would see my contacts on the list

Does this happen every time?
Yes

Other information:
Comment 1 Jonny Lamb 2009-04-23 17:32:21 UTC 
We decided that if pidgin has an account with port 5222 but no host name set, then it should ignore the port field, as a special case in XMPP.

I'll get onto this soonish.
Comment 2 Jonny Lamb 2009-06-05 14:06:23 UTC 
I've fixed this in the following branch:

http://git.collabora.co.uk/?p=user/jonny/empathy.git;a=shortlog;h=refs/heads/579992

The other commit also gets around a "bug" in importing accounts from pidgin.
Comment 3 Jonny Lamb 2009-06-05 14:24:46 UTC 
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.