Oliver Jeeves wrote:
Package: gajim
Version: 0.12.3-1
Recently, I had to use a custom hostname to connect to my jabber service
temporarily. I carried out the following steps:
1. Goto Edit -> Accounts to bring up the accounts dialog
2. Select the account, click the Connection tab
3. Tick the 'Use custom hostname/port' checkbox
4. Edit the hostname, but left the existing port value alone (the
default value is 5222, which was correct)
5. Click close
After still not being able to connect to the jabber service, we resorted
to carrying out a packet capture, and found that gajim was trying to
connect to port 0 on the server.
Changing the port value to 5223 caused it to try and connect to port
5223 as expected.
Changing the port value back to 5222 caused it to try and connect to
port 5222.
It would seem that the default values in the hostname and port input
boxes in the accounts dialog don't have any effect until they are
changed. The value in these boxes should be what is actually being used,
even if not explicitly edited by the user.
Are you sure you use 0.12.3? You restarted Gajim after you upgraded to
the very recent 0.12.3 version?
Because this bug was in 0.12.1, but it has been fixed in 0.12.3
--
Yann
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
