Bug 125219

Summary: irc-channel is not re-connected, if kopete goes offline and back online
Product: [Unmaintained] kopete Reporter: S. Burmeister <sven.burmeister>
Component: IRC PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: mega, yojoe
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description S. Burmeister 2006-04-09 13:29:21 UTC
Version:           0.12 svn (using KDE KDE 3.5.2)
OS:                Linux

If I am in some IRC-channel and the IRC plug-in goes offline and then back online again, the channel is shown as online, yet I do not receive any messages. I think this is because kopete does not re-connect to the channel, which is not obvious to the user, since the other users in the channel are shown and one can send messages in that chat-window without an error-message.

Expected behaviour would be to re-connect any channels with an open chat-window, or notify the user that one is not connected to the opened channel anymore.
Comment 1 Reinhold Kainhofer 2007-02-09 13:22:49 UTC
*** Bug 135922 has been marked as a duplicate of this bug. ***
Comment 2 Gábor Melis 2008-11-27 09:08:26 UTC
Still happens on Debian Lenny with kopete 0.12.7. With the shaky network connection that I have, this is very frustrating.
Comment 3 Alexander Rieder 2009-02-09 17:44:44 UTC
SVN commit 923876 by arieder:

Join to the previously opened channels again on reconnect

CCBUG: 125219


 M  +3 -0      ircaccount.cpp  
 M  +33 -5     libkirc/client/kircclientchannelhandler.cpp  
 M  +2 -0      libkirc/client/kircclientchannelhandler.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=923876
Comment 4 Andrew Crouthamel 2018-11-02 04:16:48 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 5 Andrew Crouthamel 2018-11-16 02:49:02 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?

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2022-12-08 23:51:09 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 7 Bug Janitor Service 2022-12-23 05:21:03 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-01-07 05:23:42 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!