Version: 0.80.2 (using KDE 1.2) OS: Linux When a user goes into standby (suspend2ram) mode (e.g. simply by clicking the power button on her laptop or closing the laptop lid), Jabber messages sent to the user are lost. Reproducible: Always Steps to Reproduce: 1. Configure KDE such that when pressing the power button, the system goes into "suspend to RAM" mode. 2. Be online using a Jabber account in Kopete 3. Press the power button. (The system goes into suspend2ram mode) 4. Let someone send you a message to your Jabber account. 5. Press the power button. (The system wakes up from the suspend2ram mode). Actual Results: The message sent to your Jabber account is lost. Sending the system into "suspend to ram" is not noticed by the Jabber server because Kopete does not disconnect from it. Expected Results: The message sent to your Jabber account is not lost. Sending the system into "suspend to ram" mode should make Kopete directly (e.g. when Kopete notices the system going into standby mode) or indirectly (e.g. when Kopete notices the network going to be disconnected) disconnect from the Jabber server _before_ the network is being brought down.
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!