Description of problem: Kile is opened with multiple (or just one) documents. In the evening, I usually put my computer to hibernate. Doing so causes Kile to close all open documents and initiating the cleaning process. This is defeating the purpose of hibernating, as one cannot properly resume work at where interrupted. System Info: Fedora 18 with Gnome as desktop. I use the shutdown/hibernate entry from the menu. There is a confirmation dialogue popping up upon which Kile closes all open documents. It also initiates some form of inhibitor, as I sometimes see a warning that kile wants to interrupt the shutdown/hibernate. For shutdown, this happens without any additional plugins installed. For hibernate, the "Frippery Shut Down Menu" extension is required. I guess, the extensions alters the usual shutdown dialogue to add the hibernate and suspend options. For shutdown, this also does not save the currently running session, i.e., all open documents. One starts with a 'blank' kile upon next start. Version-Release number of selected component (if applicable): All versions newer than 2.0 How reproducible: everytime Steps to Reproduce: 1. Open Kile 2. Open a documents (does not matter how many, one is enough) 3. Put computer to hibernate Actual results: Kile closes all open documents Expected results: Kile should keep documents open or restore on restore. Additional info: Initiating Hibernate from shell through pm-hibernate does not cause this behavior. Taking the route through the gnome-shell does. I guess that it has to do with D-Bus? This was also filled at Fedora bugzilla under #958651, but I was referred here.
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!
Michael, is it still an issue for 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!