Version: (using KDE 4.3.0) OS: Linux Installed from: Ubuntu Packages I use Kopete to connect to a groupwise messenger system on our local network. I generally have this connected all day long. At least 4 or 5 times during the course of the day I receive a dialog box saying "Kopete was not able to connect to the GroupWise Messenger server account for 'username'. Please check your server and port settings and try again." (where username is my username) I got to the client and set my status to online and immediately I am connected back again and all works well for an hour or so. Anywhere from 20 minute to two hours later, it happens again. Users of other clients are not experiencing the problem. Connecting to kopete with gdb or running kopete from the command line (in both cases, with --nofork) does not provide any error output when this happens -- both are silent when the error pops up. Not sure what the problem could be, what should I look at next?
Having a packet dump of the network traffic on the groupwise messenger ports would be helpful since there's nothing in the debug output.
I have a packet dump, but I don't think my employer would be comfortable with me posting it to a public bugtracker (IP addresses and so forth). Is there a more discreet way I can share it with those who will be working on it? From what I can see, my machine is periodically sending the server packets flagged PSH, ACK (with bad checksums, incidentally) which initiates an interchange between my machine and the server. This seems to be the same series of packets regardless of whether I get a disconnect or not, with the exception that when there is a disconnect the interchange ends with my machine sending a packed flagged RST, ACK. I don't know if that helps or not.
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? 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!