[Konversation-devel] [konversation] [Bug 330201] New: Reconnect doesn't work properly, if using a single identity only
Hans-Peter Jansen
hpj at urpla.net
Mon Jan 20 13:51:22 UTC 2014
https://bugs.kde.org/show_bug.cgi?id=330201
Bug ID: 330201
Summary: Reconnect doesn't work properly, if using a single
identity only
Classification: Unclassified
Product: konversation
Version: 1.5
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: konversation-devel at kde.org
Reporter: hpj at urpla.net
The configure settings reconnect delay and reconnect retries is misleading,
since when sitting behind a router, that is typically reconnecting every 24
hours, the reconnect most often fails,
if a single nickname is used only. This happens, when a classical ifup based
network setup is used at least.
Reproducible: Always
Steps to Reproduce:
1. set reconnect delay to 30 secs, retries to unlimited, limit yourself to a
single identity, and connect to irc.freenode.net:6667
2. forcefully disconnect your router
3. watch the server log in konversation
Actual Results:
A dialog appears, saying that the nickname is in use already, and the reconnect
is canceled.
Expected Results:
Unless reconnect retries are exhausted, reconnect attempts should be made
Due to the _quick_ reconnect or due to a protocol problem, the nickname is
still marked as used on the server and the dialog "No nicknames were accepted
(irc/server.cpp:1209)" appears. The dialog times out and returns no new
nickname -> connection is disconnected in irc/inputfilter.cpp:1252.
Although unlimited reconnect attempts were chosen, the reconnect attempt stops
after the first try!
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Konversation-devel
mailing list