Bug #163
bad network connection causes random nicks to be used
Status: | Closed | Start: | 04/05/2009 | |
Priority: | High | Due date: | ||
Assigned to: | Mirco 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=hyperair@155.69.201.250) has joined #linuxnus
[15:36] * hyperair_ (n=hyperair@155.69.201.250) has joined #linuxnus
[15:36] * hyperair (n=hyperair@155.69.201.250) 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=hyperair@155.69.201.250) has joined #linuxnus
[16:28] * hyperair (n=hyperair@155.69.201.250) Quit (Nick collision from services.)
[16:28] * hyper323 is now known as hyperair
[16:34] * hyper676 (n=hyperair@155.69.201.250) has joined #linuxnus
[16:34] * hyperair (n=hyperair@155.69.201.250) Quit (Nick collision from services.)
[16:34] * hyper676 is now known as hyperair
}}}
Associated revisions
Revision f04e1af75bed94df3bebdbc188d29c15d8cbeefd
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 5649 days ago
- Target version set to 0.6.4
Updated by Mirco Bauer 5581 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset f04e1af75bed94df3bebdbc188d29c15d8cbeefd.