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 334609 - Connection impossible
Connection impossible
Status: RESOLVED DUPLICATE of bug 331664
Product: gossip
Classification: Deprecated
Component: General
0.10.x
Other All
: Normal blocker
: ---
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-15 06:13 UTC by Peter R. Torpman
Modified: 2006-03-15 15:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Peter R. Torpman 2006-03-15 06:13:28 UTC
Please describe the problem:
I try to connect to our server (e.g server.company.com) using my user (e.g
username), but it does not work anymore. With version 0.8x it worked like a dream.
It works with Gaim, but with Gossip it ain't working any more.

The username is incorrect the server says... Probably a connection is performed
using 'username@server.company.com' as a username instead of just 'username.
 
Also, the editing of account details are reset, i.e when changing username, it
is changed back automatically by Gossip when I press the 'Connect' button.

Steps to reproduce:
1. Add account
2. Specify 'username'
3. Specify 'server.company.com'
4. Press 'Connect'


Actual results:
Not a thing. 

Expected results:
A connection should be established.

Does this happen every time?
Yes!

Other information:
Comment 1 Peter R. Torpman 2006-03-15 06:26:07 UTC
Just ran it with LM_DEBUG=ALL and this is the result:

*** Connecting to: server.company.com:5222
Going to connect to server.company.com
Trying 10.xx.yy.zz port 5222...

SEND:
-----------------------------------
<?xml version='1.0' encoding='UTF-8'?>
-----------------------------------
*** Opening stream...
SEND:
-----------------------------------
<stream:stream xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" to="chef.ks.rd.tieto.com" id="msg_1">
-----------------------------------

RECV [148]:
-----------------------------------
'<?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' id='4417B27A' xmlns='jabber:client' from='server.company.com'>'
-----------------------------------
*** Read: 148 chars
LM-PARSER: ATTRIBUTE: xmlns:stream = http://etherx.jabber.org/streams
LM-PARSER: ATTRIBUTE: id = 4417B27A
LM-PARSER: ATTRIBUTE: xmlns = jabber:client
LM-PARSER: ATTRIBUTE: from = server.company.com
LM-PARSER: Trying to close node: stream:stream
LM-PARSER: Have a new message
*** New message with type="stream:stream" from: chef.ks.rd.tieto.com
*** Stream received: 4417B27A
*** Disconnecting from: server.company.com:5222

SEND:
-----------------------------------
</stream:stream>
-----------------------------------
Comment 2 Martyn Russell 2006-03-15 09:00:04 UTC
This sounds like the same problem seen here:
http://bugzilla.gnome.org/show_bug.cgi?id=331664

Basically we made a decision to make the username "username@server.com/resource" but since, we have changed that since it doesn't feel right so the next version of Gossip we release this weekend will revert that.

To fix you situation, if you include the resource OR update the CVS HEAD, you should be able to continue using Gossip as usual. 

As for Gossip resetting the username when you try to connect, it does this if the username you enter is not valid.

Let me know if it is the same bug as the one I have linked in here.
Comment 3 Peter R. Torpman 2006-03-15 13:03:11 UTC
Hi!
Yes, I think it is the same fault. Tried to edit the xml file, but I did not
get it right anyways...

Looking forware to 0.10.2 then ;-)

Cheers,
/Peter
Comment 4 Martyn Russell 2006-03-15 15:06:18 UTC
;)

*** This bug has been marked as a duplicate of 331664 ***