[Konversation-devel] [Bug 147473] New: No nicknames from the identity were accepted by the connection

[Lars DIECKOW]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147473         
           Summary: No nicknames from the identity were accepted by the
                    connection
           Product: konversation
           Version: 1.0.1
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konversation-devel kde org
        ReportedBy: lars.dieckow googlemail com


Version:           1.0.1 (using KDE 3.5.7 "release 10.1" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.2-34-default

This is related to bug 131399 and possibly bug 85528.

How to reproduce:
For one identity, I have two nicks set up, foo and foo_. I connect to
the server using foo, then during the session change manually to foo_.
Later desaster strikes (for instance, the ISP's daily disconnect) and
I lose the connection to the server.

What should happen:
Konversation wraps around the list of defined nicks and picks the
first one again, foo. With this nick, it reconnects to the server.

What really happens:
Konversation thinks it is all out of nicks. It pops up the dialog
'No nicknames from the "%1" identity were accepted by the
connection "%2".'. Meanwhile there's no reconnect at all.

I enter foo as nick and confirm the dialog and the program reconnects
successfully. This proves that foo is really not in use, Konversation
just thinks it is.