Bug 37121 - LibO repeatedly freezes after resuming laptop from sleep
Summary: LibO repeatedly freezes after resuming laptop from sleep
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-11 17:35 UTC by Gorka Navarrete
Modified: 2015-07-18 17:27 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gorka Navarrete 2011-05-11 17:35:10 UTC
After waking up from suspend having a LibreOffice document opened, Libreoffice becomes unusable, freezing, etc. There is a long and old, but still prevalent, description of the problem in Launchpad. The problems it's been with us more than 2 years now.

https://bugs.launchpad.net/compiz/+bug/185600

This happens at least in Ubuntu 64-bits and seems somehow related to compiz.
Comment 1 cory dodt 2011-10-10 11:33:12 UTC
Just thought I'd post that I cannot find a good workaround. I did find a *bad* workaround, which is to let the power management daemon just kill off soffice. 

The reason this is better than the current bug is that the current bug has the potential to completely hang the system if you fail to kill soffice quickly. It's horrible, but I haven't found anything else that works. (One poster in the original launchpad bug suggested using compiz -replace in a pm.d script, but that did not work for me.)

Bad workaround
--------------
Create a file:
    sudo touch /etc/pm.d/sleep.d/20_kill_soffice
    sudo chmod +x /etc/pm.d/sleep.d/20_kill_soffice

Add these contents:

#!/bin/bash

PATH=/sbin:/usr/sbin:/bin:/usr/bin

SELF=kill-soffice
COMMAND=

# pm-action(8) - <action> <suspend method>
#
# On suspend|hibernate, kill soffice due to compiz-related hang:
#  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/185600 

case "${1}" in
        hibernate)
            ;;
        resume|thaw)
            # hope soffice's recovery function works.
            pkill -f soffice.bin
            ;;
esac
Comment 2 cory dodt 2011-10-10 11:34:56 UTC
(In reply to comment #1)
> Just thought I'd post that I cannot find a good workaround. I did find a *bad*
> workaround, which is to let the power management daemon just kill off soffice. 
> 
> The reason this is better than the current bug is that the current bug has the
> potential to completely hang the system if you fail to kill soffice quickly.
> It's horrible, but I haven't found anything else that works. (One poster in the
> original launchpad bug suggested using compiz -replace in a pm.d script, but
> that did not work for me.)
> 
> Bad workaround
> --------------
> Create a file:
>     sudo touch /etc/pm.d/sleep.d/20_kill_soffice
>     sudo chmod +x /etc/pm.d/sleep.d/20_kill_soffice
> 
> Add these contents:
> 
> #!/bin/bash
> 
> PATH=/sbin:/usr/sbin:/bin:/usr/bin
> 
> SELF=kill-soffice
> COMMAND=
> 
> # pm-action(8) - <action> <suspend method>
> #
> # On suspend|hibernate, kill soffice due to compiz-related hang:
> # 
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/185600 
> 
> case "${1}" in
>         hibernate)
>             ;;
>         resume|thaw)
>             # hope soffice's recovery function works.
>             pkill -f soffice.bin
>             ;;
> esac

Line breaks got a little messed up - you will have to delete the line where I mention the bug URL, as that was supposed to be a comment.
Comment 3 Björn Michaelsen 2011-12-23 12:02:56 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 4 Gorka Navarrete 2011-12-24 15:39:21 UTC
The problem persists in LO 3.5 beta 2 in Ubuntu 11.10.
Comment 5 Björn Michaelsen 2011-12-27 08:16:48 UTC
possibly related to https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/745836
Comment 6 Christopher M. Penalver 2011-12-31 04:50:56 UTC
Gorka Navarrete, please do not toggle the Version. For more on this please see: http://wiki.documentfoundation.org/BugReport_Details#Version
Comment 7 Gorka Navarrete 2012-04-08 02:26:21 UTC
Still having the problem in LibreOffice 3.5.1.2 Build ID: 350m1(Build:102) with Ubuntu 11.10.

If the system is powerful enough (8 cores, 16Gb RAM, SSD disk, etc.) it is annoying but not critical. With an inferior system, the computer becomes unusable and the only way forward is closing all LO instances.

There is anything I can o to help triage this?
Comment 8 Björn Michaelsen 2013-02-23 19:48:37 UTC
closing as WORKSFORME as per: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/185600/comments/71
Comment 9 Gorka Navarrete 2013-03-27 13:02:32 UTC
I think I might have made a mistake and attributed an improvement in the situation to LO instead of to a faster computer. It is true that now Libreoffice does not render the system unusable after waking up from suspend but the problem somehow persists.

With a modern computer what you would notice now is a CLEAR slowing in LO (e.g. when scrolling down the page LO is slower than normal and somehow unresponsive).

You still have to completely close LO and reopen it again for it to work properly.
Comment 10 Joel Madero 2014-11-02 16:11:36 UTC
This doesn't look like it was ever confirmed by the QA team. Moving to UNCONFIRMED.
Comment 11 tommy27 2014-11-03 19:41:05 UTC
@Gorka Navarrete
please give update of the bug status with current LibO 4.3.3.2 or 4.2.7.2 release
Comment 12 retired 2014-11-16 08:41:10 UTC
Setting to NEEDINFO until more detail is provided.

After providing the requested info, please reset this bug to UNCONFIRMED (should it be persisting) or WORKFORME (should it be solved with a newer LO version).
Comment 13 QA Administrators 2015-06-08 14:29:01 UTC
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 INVALID
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!

This NEEDINFO Message was generated on: 2015-06-08

Warm Regards,
QA Team
Comment 14 QA Administrators 2015-07-18 17:27:36 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO

Message generated on: 2015-07-18