Bug #163

avatar

bad network connection causes random nicks to be used

Added by Mirco Bauer 5559 days ago. Updated 5431 days ago.

Status:Closed Start:04/05/2009
Priority:High Due date:
Assigned to:avatarMirco Bauer % Done:

100%

Category:Engine IRC
Target version:0.6.4
Complexity:

Found in Version:

Votes: 0

Description

When the network connection goes bad and smuxi reconnects, at some point it will use the random fallback nicknames instead of trying the user-defined nicks first.

Here a log of such behavior: {{{
[15:34] * hyperair (n=) has joined #linuxnus
[15:36] * hyperair_ (n=) has joined #linuxnus
[15:36] * hyperair (n=) Quit (Nick collision from services.)
[15:36] * hyperair_ is now known as hyperair__
[15:37] * hyperair__ is now known as hyperair
[16:28] * hyper323 (n=) has joined #linuxnus
[16:28] * hyperair (n=) Quit (Nick collision from services.)
[16:28] * hyper323 is now known as hyperair
[16:34] * hyper676 (n=) has joined #linuxnus
[16:34] * hyperair (n=) Quit (Nick collision from services.)
[16:34] * hyper676 is now known as hyperair
}}}

Associated revisions

Revision f04e1af75bed94df3bebdbc188d29c15d8cbeefd
Added by Mirco Bauer 5431 days ago

Disabled the buggy nick handling of the SmartIrc4net library and provide an own one. After a disconnect reset the nickname list so the best nick will be used again for the next connection attempt. (closes: #163)

History

Updated by Mirco Bauer 5498 days ago

avatar
  • Target version set to 0.6.4

Updated by Mirco Bauer 5431 days ago

avatar
  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF