Version: 0.80.2 (using KDE 4.3.3) OS: Linux Installed from: Archlinux Packages I have been having this issue since KDE 4.3.1, although I'm not precisely sure. Kopete has been frequently disconnecting from ICQ with no apparent reason. It happens quite randomly and I can't see any pattern there. It can happen every 5 minutes or 2 hours. The only error I get is "(ICQ UIN) disconnected: Unknown error" popup window, then Kopete sucessfully reconnects in most cases. I have experienced similar behaviour on two machines in my network both running the same version on KDE. One is Arch linux and another Gentoo based. I tried fresh install of Arch, changing account priority in Kopete, altering the account setting to no avail. If I run Kopete through console, there is no mention of the disconnection in the output. There are two other accounts in my profile, MSN and Jabber, which have been working perfectly. Other clients like Finch work just fine too.
I seem to have this issue too. Kopete began producing these error messages at approximately the same time I changed my DSL modem from 2Wire to D-Link DSL-2640B. I am not sure if it is the culprit; I'll try temporarily switching back to 2Wire to see if it makes a difference.
You might be onto something, both of my machines suffering from this weird issue are behind ASUS WL-600g ADSL router, one on wireless and another on wired connection. I used to have OvisLink ARM-104 and Kopete worked fine at that times. I will check how does it work if I connect through my uni wifi network.
1. I tried with old modem (2Wire); it seems to work okay. At least I didn't notice a single Kopete disconnect in ~20 minutes, while with other modem (D-Link DSL-2640B) it disconnects every 5-10 minutes. 2. I ran Wireshark and captured the moment when disconnect happens. See attached screenshot. Normally, the "AIM keep-alive" packet is followed by an ACK from AOL server. However, immediately after a keep-alive packet (#924), Kopete closed the connection. Note that the packet #925 which has FIN+ACK originated from 192.168.1.3 - which is my laptop. So, for some reason Kopete decided to close the connection. I saved the capture file, so I could provide any further information upon request. Could anybody of Kopete developers suggest what further debugging could be done? BTW, I am using a different distribution than original poster: Kubuntu 9.10.
Created attachment 38919 [details] Wireshark screenshot at the disconnect time #924: Kopete sends a keep-alive #925: Kopete closes the connection #926: AOL acknowledges keep-alive #927: AOL acknowledges connection closure #928: connection is closed #948: new connection is being established
I've just tired the experiment with wireshark and I got exactly the same results.
Could you show me more packet before the #924, or send me the log to kedgedev (at) gmail.com
madcatx as you have gentoo you could recompile Kopete with debug flag and then check all Kopete entries in kdebugdialog and start Kopete from console ... this could tell us more.
Created attachment 38944 [details] Debug info dumped by kopete
As I'm not possible to gather any info from my gentoo machine right now, I tried to get something out of my arch based machine. I've captured what kopete dumps to console from the moment of the random disconnection to the succesfull reconnect. I had all kopete entries in kdebugdialog enabled. This pattern seems to be the same any time this random disconnection occurs. I will see if there is any difference on my gentoo machine when possible.
madcatx could you capture more lines before the ClientStream::socketError: error: 1 approximately 30 lines before should be enough.
OK, here it goes, I didn't post it before because it didn't seem to be of any relevace.
Created attachment 38950 [details] More debugging info
I have tried to connect with Kopete through another network than my own and ICQ has stayed online for over an hour, so it suggests Alexeys idea that these random disconnections have something to do with router.
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!
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!