[Konversation-devel] [Bug 235186] New: Timed reconnect cannot be cancelled without closing whole network tab
Jonas Thiem
contact at eloxoph.com
Fri Apr 23 17:37:03 CEST 2010
https://bugs.kde.org/show_bug.cgi?id=235186
Summary: Timed reconnect cannot be cancelled without closing
whole network tab
Product: konversation
Version: 1.2.3
Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: konversation-devel at kde.org
ReportedBy: contact at eloxoph.com
When getting kicked from a server Konversation will depending on the
configuration attempt a reconnect in X seconds.
Now if an actual reconnect takes place it is possible to stop it using /quit or
/disconnect.
But during that X seconds until the reconnect attempt gets actually triggered,
there seems to be no way to unqueue that reconnect attempt except
a) being very fast when it actually happens and kill it off before e.g. the
server ban kills it off and another reconnect gets scheduled (assuming you're
throttled/banned)
b) closing the whole network tab with all open channels/queries to stop any
timed reconnect attempts although you probably wanted to reuse the tabs lateron
after some delay.
This is especially annoying e.g. when getting throttled by a server during a
reconnect so any additional reconnect attempt will enhance/prolong the
throttling and an actual reconnect with subsequent server killoff due to the
throttle will happen so fast that you can't type /quit while it happens.
So to stop the reconnecting you need to close the whole network tab to give
that throttle a chance to calm down so you may actually get back to that server
after some time - but then of course with all channels/queries you had
previously opened closed.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Konversation-devel
mailing list