Version: 1.0.0 (using KDE 4.5.2) OS: Linux I am often in Eduroam, the university network, and get disconnected quite a few times. Every time wicd reconnects, Kopete disconnects and reconnects, but sets it's status to Online (instead of anything else that it was before). Reproducible: Always Steps to Reproduce: 1. Connect to a wireless network using wicd, set Kopete to "Away" (or something else) 2. Do something to lose connectivity. Wicd will disconnect, causing Kopete to disconnect too. 3. Reinstate connection. Kopete reconnects, being Online. Actual Results: Status is set to Online. Expected Results: Status should be restored to "Away" (or whatever). OS: Linux (x86_64) release 2.6.34-tuxonice-r6-richBOOK Compiler: x86_64-pc-linux-gnu-gcc Kopete: 1.0.80 (KDE 4.5.2)
Still happens with 1.0.80 (KDE 4.5.3)
I have the same problem with git master as of 17.8.2012. After a network reconnect (NetworkManager here), kopete goes to the state that is set as "Initial status" in the Behaviour section of settings (i.e. as if it has just started). This is bad, because although I wan't kopete to go immediately online when I start it, If I manually set it to offline while running, I don't wan't it to recconnect after a network reconnect... Instead of the initial status, it should go to the status last set by user.
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!