| Summary: | User quit/nick changes not always noted | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | Rael Daruszka <rdaruszka> |
| Component: | protocol | Assignee: | Konversation Developers <konversation-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | hein |
| Priority: | NOR | ||
| Version: | 1.5-rc1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Rael Daruszka
2007-10-25 11:00:07 UTC
The critical information you need to tell us here is on what server / network you see this happening. It's most likely a parsing problem, so we need access to the raw protocol stream the server is sending. As an example, Konvi 1.0 fixed a similar problem with parsing UnrealIRCD's somewhat unorthodox message format for QUITs without a quit message. Server/Network is a semi-private one, generally no more than a couple dozen people on at a time. I believe the following should have all the server version information you need. [12:48:14] [Info] Looking for server nbtsc.org:6667... [12:48:14] [Info] Server found, connecting... [12:48:14] [Info] Connected; logging in... [12:48:14] [Notice] -castle.nbtsc.org- *** Looking up your hostname... [12:48:14] [Notice] -castle.nbtsc.org- *** Found your hostname (c-67-170-57-126.hsd1.wa.comcast.net) [12:48:18] [Notice] -castle.nbtsc.org- Welcome to NBTSC! [12:48:18] [Welcome] Welcome to the NBTSC IRC Network Rael!rdaruszka@c-67-170-57-126.hsd1.wa.comcast.net [12:48:18] [Welcome] Your host is castle.nbtsc.org, running version InspIRCd-1.1.9+IsleOfMull [12:48:18] [Welcome] This server was created 18:28:54 Jun 18 2007 [12:48:18] [Welcome] Server castle.nbtsc.org (Version InspIRCd-1.1.9+IsleOfMull), User modes: RSinosw, Channel modes: MRSbchiklmnopstvz [12:48:18] [Support] Rael WALLCHOPS WALLVOICES MODES=19 CHANTYPES=# PREFIX=(ohv)@%+ MAP MAXCHANNELS=20 MAXBANS=60 VBANLIST NICKLEN=31 CASEMAPPING=rfc1459 STATUSMSG=@%+ CHARSET=ascii [12:48:18] [Support] Rael TOPICLEN=307 KICKLEN=255 MAXTARGETS=20 AWAYLEN=200 CHANMODES=b,k,l,MRScimnpstz FNC NETWORK=NBTSC MAXPARA=32 ELIST=MU WATCH=32 Here is the raw message from the server for a quit that did work: :test2!rael@localhost QUIT :Quit: leaving And a raw of a quit with no quit message which also worked: :test!rdaruszka@c-67-170-57-126.hsd1.wa.comcast.net QUIT :Client exited Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Since there was another request for information (5 years after the previous, 16 years after the report) I dug up my login info to reply: I no longer use IRC and do not have the ability to test anything related to this ticket. Beyond my previous posts I cannot provide any information to assist with diagnosing if there is still an issue or what the issue may be. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |