Hi, On my Ubuntu 16.04 LTS LO crashes reproducibly when my system goes to sleep (suspend) and wakes up. The crash happens after wake up shortly after 1-2 seconds. If I log in immediately, I see the crash happening (LO goes to document recovery mode). If I don't login immediately I find LO in document recovery mode already. I guess, user logging into system is not the trigger but the wake up process itself. I tried gdb debugging. 1) Run LO. 2) gdb 3) attach <pid> 4) Suspend the system 5) Login to see crash LO doesn't crash with gdb attached but freezes. It doesn't recover from the freeze. I am stuck at this point. I have never lost data due to this but it is annoying (therefore the severity "normal"). Best, Saren
Tested with LO 5.4.3.2 (TDF build) / Ubuntu 17.04, and encountered no crash when the computer came back from sleep.
No crash for me in Fedora 26, Version: 6.1.0.0.alpha0+ Build ID：d8c0051c6c0400aae6e0a440e83c2c29979347f7 CPU 线程：4; 操作系统：Linux 4.13; UI 渲染：默认; VCL: gtk2; Locale: zh-CN (zh_CN.UTF-8); Calc: group threaded
Hi Saren Tasciyan, Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongsidethe standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Dear Bug Submitter, 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-20180731
Dear Bug Submitter, 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-20180903
Looking back at this, it seems kind of similar to bug 119028, which is OpenGL-only, and I haven't been able to test it on Linux.