Bug 263157 - Server kicks are not shown
Summary: Server kicks are not shown
Status: CONFIRMED
Alias: None
Product: konversation
Classification: Applications
Component: protocol (show other bugs)
Version: 1.5-rc1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-14 16:21 UTC by Bernd Buschinski
Modified: 2013-04-15 02:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Buschinski 2011-01-14 16:21:59 UTC 
Version:           Git (using KDE 4.5.95) 
OS:                Linux

in Quakenet there are 2 "network bots" fishbot and catbot, catbot hunts fishbot and kicks it, or rather the server kicks fishbot as catbot does not have OP to kick fishbot.
However the kick is not shown in konversation, fishbot is still shown in the channel until you rejoin.

rawlog:
[16:08] >> :*.quakenet.org KICK #somechan fishbot :*bite* *munch* *munch*%0A


Reproducible: Always

Steps to Reproduce:
- join Quakenet #somechan (doesn't matter as long as you are op)
- /invite fishbot #somechan
- /invite catbot #somechan
- wait a few seconds

Actual Results:  
- kick is not shown and fishbot is still in the nicklist

Expected Results:  
- catbot/the server kicks fishbot and it should be removed from nicklist

There is no visible error feedback that something couldn't be parsed
Comment 1 Bernd Buschinski 2011-01-19 23:49:51 UTC 
ok I tracked it down to

InputFilter::parseLine

if ((!prefix.contains('!')) && (prefix != m_server->getNickname()))
in line 147

with "*.quakenet.org" as prefix it seems not all prefix must contain a '!'
to be a client command.
My problem now I don't know how to identify a "100% safe" client command
Comment 2 Eike Hein 2012-04-09 00:48:45 UTC 
Updates?