Description: Hi hello. I've been having a problem now pretty much ever since Kubuntu 18.04 came out where whenever I happen to have libreoffice open on my computer when it goes into suspend mode, it prevents it from waking up. The fans turn on and the lights turn on, indicating it has awoken but the screen never turns on, remains idle. You can reproduce the error by setting your powerdevil settings to suspend the PC after any number of minutes and then opening libreoffice and waiting for said time to elapse. Your screen will never wake up but there may be other indicators that give the impression that the PC is on. Steps to Reproduce: 1. Set kubuntu 18.04 powerdevil settings to suspend the PC after any number of time of your choosing (for testing purposes just use 1 minute) 2. open libreoffice writer 3. wait for the time until suspend mode is activated to elapse 4. Attempt to wake the PC from suspend Your screen should remain idle but your computer lights and fans might activate. Actual Results: Screen remains idle when attempting to resume from suspend. Computer does not awake from suspend. Expected Results: The software should not lock me out of my computer. I am very worried that my documents will be destroyed some time because of this. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Very worried that my documents will be corrupted and destroyed by this error since I have to forcefully reboot my PC every time it happens.
What hardware is this occurring on? What Linux distro (and kernel) are you running? When this occurs, can you get the screen back by holding down CTRL + ALT + F2, and then CTRL + ALT + F1? Are you 100% certain this only occurs when LibreOffice is open? Finally, have you tried uninstalling and performing a clean install? On Ubuntu based systems, this can be achieved using: sudo apt remove --purge libreoffice-* sudo apt autoremove sudo apt install libreoffice
In regards to losing your work - try setting your automatic recovery for every 5 minutes (or so): 1. Tools > Options > Load/Save > General 2. Make sure "Save AutoRecovery informatoin every" is checked. 3. Set the number of minutes. This way, in a worse case scenario, you'll lose 5 minutes of work. Hopefully you won't lose any work if you just leave your machine on for 5 minutes after it resumes from suspend (instead of hard-resetting it too early).
Thanks, Andy. Let's set the status to NEEDINFO while we wait for the answers.
I'm gonna have to bump this thread because I'm having the exact same problems in the exact same version of libreoffice still. I thought I fixed it somehow but I'm pretty sure my "fix" was just closing libreoffice before I put the computer to sleep every time.
and of course I uninstalled and reinstalled. thats the first thing I did. and changing the autorecovery settings is really putting a bandaid on a gaping wound.
Kernel version 4.15.0-39-generic I already said which distro I'm using. Specs: ASUS M5A78L-M PLUS/USB3 motherboard Graphics card: ASUS GTX 460 1gb AMD FX-6300 processor 6gb RAM (I've ran a ram check already, its fine) Corsair 500w power supply I dont think my specs have anything to do with it. It's probably because I have an old install of my distro (NOT Libreoffice which I have reinstalled multiple times since getting this issue). But at this point I'm not willing to reinstall, getting my system back to where I am now would be a rather arduous process.
Again, I'm talking about the DISTRO. I dont want to reinstall my DISTRO for various reasons. I've been reinstalling libreoffice plenty of times with no results.
(In reply to Andy Turfer from comment #1) > When this occurs, can you get the screen back by holding down CTRL + ALT + > F2, and then CTRL + ALT + F1? What about this, Elias?
RE: Comment 8 I just got the error again a few minutes ago and had to restart my PC (Yes, libreoffice was open). I tried doing ctrl+alt+f1 then ctrl+alt+f2 then ctrl+alt+f1 again, it didn't bring the system back to life unfortunately.
I've now upgraded my Libreoffice to the newest version available for Kubuntu 18.04, version 6.0.7.3, and incredibly the error persists! How can this be?
If you run an appimage version instead, does the same problem occur? https://libreoffice.soluzioniopen.com/
Hello Elias, Could you please try to reproduce it with LibreOffice 6.2.0.2 from https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Elias, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Elias, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp