Bug 168891 - 1st packet byte removed after whois
Summary: 1st packet byte removed after whois
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: protocol (show other bugs)
Version: 1.0.1
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-11 08:20 UTC by d0wn
Modified: 2012-04-09 00:36 UTC (History)
1 user (show)

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


Attachments
konversationrc (3.25 KB, text/plain)
2008-08-11 18:15 UTC, d0wn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description d0wn 2008-08-11 08:20:56 UTC
Version:           1.0.1 (using KDE 3.5.9)
Installed from:    Debian stable Packages
OS:                Linux

After you issue the /whois command, the next command to send, the first byte will be removed.

for example, 
/whois test
<whois info would be here>
/msg example this is a message
[02:16] [-> example] this is a message
[02:16] [Error] RIVMSG: Unknown command.

This has disconnected me due to not being able to reply to pings. i'm not sure if it should be considered a crash or not, as it doesn't actually crash the application.
Comment 1 Eike Hein 2008-08-11 15:59:27 UTC
I'm afraid I'm unable to reproduce this problem with either v1.0.1 or the recently released v1.1. There must be special circumstances in your case. It would be useful if you could tell us which IRC server you're experiencing this problem with, and if you could attach your konversationrc settings file (take care to remove any passwords first). This may also be caused by your network/router.
Comment 2 d0wn 2008-08-11 18:15:59 UTC
Created attachment 26785 [details]
konversationrc

the irc server is irc.projectparanormal.org #6667
Comment 3 Eike Hein 2008-08-11 20:01:56 UTC
I'm afraid I can't reproduce the problem with either v1.0.1 or v1.1 on the named server, with or without the attached settings file, so it's likely to be some kind of external cause on your system or in your network.