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

(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.

[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

The problem persists in LO 3.5 beta 2 in Ubuntu 11.10.

possibly related to https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/745836

Gorka Navarrete, please do not toggle the Version. For more on this please see: http://wiki.documentfoundation.org/BugReport_Details#Version

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?

closing as WORKSFORME as per: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/185600/comments/71

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.

This doesn't look like it was ever confirmed by the QA team. Moving to UNCONFIRMED.

@Gorka Navarrete
please give update of the bug status with current LibO 4.3.3.2 or 4.2.7.2 release

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).