[Konversation-devel] [Bug 128786] New: Konversation does not respond to other clients' "/leave" on Undernet servers

Dave Ewart davee at ceu.ox.ac.uk
Wed Jun 7 20:49:49 CEST 2006


------- 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=128786         
           Summary: Konversation does not respond to other clients' "/leave"
                    on Undernet servers
           Product: konversation
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konversation-devel kde org
        ReportedBy: davee ceu ox ac uk


Version:           0.19 #3100 (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When connected to any undernet IRC server (either irc.undernet.org and derivatives, or a locally-running ircd-ircu instance), the effects of other clients' "/leave" are apparently ignored by Konversation.  Example:

In Konversation:

  /server irc.undernet.org
  /join #randomircchannel

In $OTHER_CLIENT connected from elsewhere

  /server irc.undernet.org
  /join #randomircchannel

At this point, Konversation shows:

"--> otheruser has joined this channel"

as expected.

In $OTHER_CLIENT

  /leave

which causes NO OUTPUT in Konversation at all, rather than the expected "otheruser has left this channel".  Konversation keeps the nick corresponding to the user who has actually left in the nick list, too.

As a further example, if $OTHER_CLIENT repeatedly joins and leaves the channel, output like this is produced in Konversation:

"--> otheruser has joined this channel"
"--> otheruser has joined this channel"
"--> otheruser has joined this channel"
"--> otheruser has joined this channel"
etc.

with all the expected "... has left this channel" entries missing.

This bug appears to be completely reproducible, but confined to happening to Konversation on undernet-style servers: it doesn't happen on freenode, for example.  It also doesn't affect other clients I've tried, running on undernet-style servers (e.g. irssi, X-Chat, Chatzilla etc.): these non-Konversation clients show the "... has left this channel" response correctly.

Further, if $OTHER_CLIENT issues a "/quit" or a "/disconnect", rather than a "/leave", then this *is* noticed by Konversation:

"<-- otheruser has left this server ..."


More information about the Konversation-devel mailing list