[Konversation-devel] [Bug 111703] New: Konversation does not see messages in channels

Jan Ekholm chakie at infa.abo.fi
Mon Aug 29 13:13:46 CEST 2005


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=111703         
           Summary: Konversation does not see messages in channels
           Product: konversation
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konversation-devel kde org
        ReportedBy: chakie infa abo fi


Version:           0.18 #3016 (using KDE 3.4.2-1.2.fc3.kde, Fedora)
Compiler:          gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
OS:                Linux (i686) release 2.6.10-1.741_FC3

Sometimes Konversation seems to loose the messages of a channel. This happens after having a tab open to a channel for several days, usually there has been some network disconnect, split or something else that has disrupted the connection temporarily.

The bug does not cause a crash or error message, only all messages to a channel are dropped. I still can see all /join, /leave and /nick messages, as well as some other "admin" messages that are not directly written by some user. All normal chat is missing. Today I had two channels that were in this "dead" state, and when I left them (/leave) I saw this in the channel window that got activated:

[13:59] [442] #kubuntu You're not on that channel
[13:59] [442] #amarok You're not on that channel

Obviously Konversation thought I was on the channels, as it still received the /join:etc, but I apparently wasn't as I saw no messages and got the above errors that mean that I wasn't a member of #kubuntu or #amarok.

I have seen this bug a few times, and the channel window never has any errors in it, and the IRC-server window has nothing special in it except for normal network errors and reconnects.

Maybe one could request that Konversation either rejoins a channel or clearly marks it as inactive so that I know to rejoin it manually? 

I can provide more specific info if needed.

Best regards, 
    Jan Ekholm


More information about the Konversation-devel mailing list