Version: 1.0.1 (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux When I have high lag (sometimes around 414 ms but other times less) on irc.freenode.net (not sure about other networks) and mark myself as away (Ctrl + Alt + A) Konversation shows: [Away] You are now marked as being away. [Away] You are now marked as being away. in the chat window. It seems to happen only when there is a large amount of lag. Kubuntu 6.10 (Edgy), KDE 3.5.5 and Konversation 1.0.1 There is another bug report with a screenshot available at https://launchpad.net/distros/ubuntu/+source/konversation/+bug/72522
I can confirm this. This only happens when the server is lagging (or my internet connection is lagging). Using Kubuntu 6.10 (Edgy), KDE 3.5.5, Konversation 1.0.1
Does the same happen if you use the /away command instead?
Haven't given it a shot. I will when I get back to my computer (around Sunday) On 23 Nov 2006 08:39:46 -0000, Peter Simonsson <peter.simonsson@gmail.com> wrote: [bugs.kde.org quoted mail] Haven't given it a shot. I will when I get back to my computer (around Sunday)<br><br><div><span class="gmail_quote">On 23 Nov 2006 08:39:46 -0000, <b class="gmail_sendername">Peter Simonsson</b> <<a href="mailto:peter.simonsson@gmail.com"> peter.simonsson@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: ------- <br>You reported the bug, or are watching the reporter.<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=137758">http://bugs.kde.org/show_bug.cgi?id=137758</a><br><br><br><br><br>------- Additional Comments From peter.simonsson gmail com 2006-11-23 09:39 -------<br>Does the same happen if you use the /away command instead?<br></blockquote></div><br><br clear="all"><br>-- <br>-Freddy Martinez-<br>Kubuntu. [GNU/]Linux for human beings.<br></message>
The relevant code has been rewritten from scratch as of SVN revision 814915-815176, and I'm unable to reproduce the problem or see why it would occur. Hence I'm closing under the assumption that the problem has been dealt with. If it ends up still occuring with SVN versions post r815176 or the upcoming 1.1 release, please reopen.