Bug #895

Weird K-Line behavior

Added by windsok over 2 years ago. Updated about 2 years ago.

Status:Rejected Start date:01/18/2010
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:Quassel Client
Target version:-
Version:0.6-pre OS:Windows

Description

I was idling in #ubuntu on Freenode today when some users in the channel got K-Lined.

Strangely my client created a chat buffer for each of the K-Lined Users with the following:

[14:09:33] <-- dby (n=) has quit (K-lined)
[14:09:33] * No such nick/channel dby
[14:09:33] * No such nick/channel dby
[14:09:34] * No such nick/channel dby

I also received "no such nick/channel" notifications in the system tray

Running core on Ubuntu Linux, and client on Windows 7.

Client: Version: v0.6-pre (0.5.0+134 git-f8dcbdf)
Core: Quassel IRC: v0.6-pre (0.5.0+91 git-a8c38cb)

History

#1 Updated by EgS about 2 years ago

  • Status changed from New to Rejected

I don't think it's an issue with the k-line-handling. (mostly because there is none ;)) From an observer point of view (neither the kliner nor the klinee) the kline is absultely indifferent to a regular quit.

It wouldn't surprise me if Mr. dby was k-lined due to spamming. And most likely you will find some ctcp-requests from him in your statusbuffer. Those requests were probably not yet answered when dby was k-lined, so quassel was merely reacting to the queued ctcp-requests. since at this time dby was no longer on the network you were seeing those "No such nick/channel" messages, which are usually displayed in the current channel.

In addition: a k-line on a testnetwork did not result in the same output.

Also available in: Atom PDF