Bug 151320 - User quit/nick changes not always noted
Summary: User quit/nick changes not always noted
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: protocol (show other bugs)
Version: 1.5-rc1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-25 11:00 UTC by Rael Daruszka
Modified: 2023-02-01 05:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rael Daruszka 2007-10-25 11:00:07 UTC
Version:           1.0.1 (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

When users quit or change nicks the change is not always reflected in queries with them or the channel nick lists.

Examples that I have seen:
User comes online, I query them, they change nick, when I try to message them in the query it says user is not online.
User comes online, eventually they quit, no quit message appears in any channel/query, nicklist still lists them as online but they are not.

Sometimes it works as it should, sometimes not.  I have yet to notice a pattern to it's failures.  I've noticed this running konversation 1.0.1 under kde 3.5.8 on kubuntu 7.10 and also previously in with gentoo linux, not sure of konversation/kde versions then but it was no more than 3 months ago running the latest and greatest available at the time.

Also the watched nicks fail to give notices that users are online and fail to update in the watched nicks online tab.

Also in at least one case I have seen a user who was already in a channel get a join message as seen below:

[21:39:39] --> Victor has joined this channel (rdaruszka@c-76-20-13-184.hsd1.ca.comcast.net).

... Much talking but no quit/part messages in this period for the other user, I believe he was in the channel at all times.

[01:16:57] [Whois] Victor is rdaruszka@c-76-20-13-184.hsd1.ca.comcast.net (purple)
[01:16:57] [Whois] Victor is a user on channels: #nbtsc
[01:16:57] [Whois] Victor is online via castle.nbtsc.org (Not Back To School Camp Chat).
[01:16:57] [Away] Victor is away: I'm not here right now
[01:16:57] [Whois] Victor has been idle for 3 hours, 36 minutes, and 55 seconds.
[01:16:57] [Whois] Victor has been online since 10/24/2007 09:39:36 PM.
[01:16:57] [Whois] End of WHOIS list.
[01:34:42] --> Victor has joined this channel (rdaruszka@c-76-20-13-184.hsd1.ca.comcast.net).
[01:34:53] <-- Victor has left this server (Quit: Leaving.).

The user info appears to match my personal userinfo (the rdaruszka username) however the system had been mine previously, and there was much playing with settings so it is possible that my IRC settings on the system got copied to the new users settings.  The hostname does not match my hostname so I believe it's just mixed up settings and not any sort of bug in konversation.

It appears that any nick changes or quits that appear in the channel window will be reflected in the nicklist, but I cannot say with 100% certainty that this is so.

I have not been able to reproduce the bug intentionally, just noticed it quite frequently.  I'm not sure what else I can provide to help track this down, but I will be glad to attempt to answer any questions regarding the bug or my setup I can.
Comment 1 Eike Hein 2007-10-25 11:18:52 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.
Comment 2 Rael Daruszka 2007-10-25 22:13:23 UTC
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
Comment 3 Andrew Crouthamel 2018-11-10 03:19:10 UTC
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!
Comment 4 Andrew Crouthamel 2018-11-20 04:08:26 UTC
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!
Comment 5 Justin Zobel 2023-01-02 02:04:14 UTC
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!
Comment 6 Rael Daruszka 2023-01-02 02:14:42 UTC
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.
Comment 7 Bug Janitor Service 2023-01-17 05:13:59 UTC
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!
Comment 8 Bug Janitor Service 2023-02-01 05:03:40 UTC
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!