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 349515 - Stop button in the accounts dialog doesn't work after errors
Stop button in the accounts dialog doesn't work after errors
Status: RESOLVED FIXED
Product: gossip
Classification: Deprecated
Component: General
0.13
Other All
: Normal normal
: ---
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-01 09:24 UTC by Keywan Najafi Tonekaboni
Modified: 2006-09-09 09:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Keywan Najafi Tonekaboni 2006-08-01 09:24:20 UTC
Please describe the problem:
If you want stop a current connection attemp and push stop, while gossip tries to connect to a server, it didn't stop. In some cases it tries again to connect.

Steps to reproduce:
1. Start gossip
2. Open Edit->Accounts
3. Try to connect with a server, which take a while or manipulate the connection details (e.g. "Use SSL" while the server didn't support it, disconnect from network etc..


Actual results:
pushing the button didn't seems to do any action.  

Expected results:
the connection attemp seems to be aborted

Does this happen every time?
yes.

Other information:
If the connection is refused with errror 111 (got this information with LM_DEBUG=net), the account manager didn't react on this refuse. The icon still blinks and the button stil show "Stop". But when I click again on stop, it tries again to connect. Maybe just the GUI is not correctly updated.
Comment 1 Richard Hult 2006-08-07 23:00:17 UTC
The stop button always works for me, for example when trying to connect with weird port settings and stopping the attempt. Are you sure you are using recent versions of loudmouth and gossip?
Comment 2 Keywan Najafi Tonekaboni 2006-08-08 07:49:47 UTC
Yes, I recognize it with gossip 0.13 and LM 1.0.3. I can still reproduce it with version 0.14. I guess it is just a wron GUI represantation.

I have a jabber server on localhost, which didn't support SSL. If I try to connect to it with SSL, this happens:

Going to connect to cassini
Trying 127.0.0.1 port 5223...
Connection failed: Connection refused (error 111)

But the account bulb still blinks and the connect button show "Stop". But this button reacts as if it was "Connect" not "Stop". When I push it again this happens:

Going to connect to cassini
Trying 127.0.0.1 port 5222...
(...)

When I changened the Account information, e.g. deselect SSL, then it connect correctly when I push this "wrong" "Stop".
Comment 3 Martyn Russell 2006-08-08 08:25:16 UTC
I think this is a known error and like Richard says, you need the latest version of Loudmouth too (or actually, v1.1.2 or above):

If you don't see this message in the LM_DEBUG output:
   
    *** Disconnecting from: jabber.org:5223

Then you have an older version I think. 
Closing this bug, reopen if you still have this issue.
Comment 4 Richard Hult 2006-08-08 17:19:32 UTC
I can reproduce with lm 1.1.x, reopening.
Comment 5 Richard Hult 2006-09-09 09:24:34 UTC
Fixed in CVS, thanks. The stop button is reset into a connect button on error (although we don't show that there was an error other than in the contact list window).