Switching user while Compiz enabled makes OpenOffice.org crawl (extremely slow scrolling)

[Mahendra Tallur]

Short form : When switching back & forth to another user (such as the guest account), while Compiz is enabled and an OpenOffice.org document is opened, OpenOffice gets extremely slow until you quit / relaunch it or disable compositing.

Long form : Here's how to reproduce this issue :

1) log in to any account with Compiz enabled
2) open any OO.org text document
3) switch to another account (for instance, the guest account, that uses compositing as well)
4) switch back to the first account
5) expected behaviour : OO.org continues to work properly, smooth scrolling, reactive GUI...
--> Actual behaviour : OO.org gets unusable ; scrolling is extremely slow, the GUI takes much time to react, the X.org process eats much CPU.
6) in order to get OO.org to work properly again : either disable compositing or quit and relaunch OO.org

It doesn't seem to affect any other app.

My setup :

Ubuntu 10.04
Nvidia proprietary drivers 256.35
go-OO.org 3.2.0
Compiz enabled

[shankao (shankao)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in openoffice.org

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[penalvch (penalvch)]

Mahendra Tallur, thank you for reporting this bug and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 606558
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Could you please attach a Writer file that when open, this issue occurs with? Does LibreOffice Writer work for you?

sudo add-apt-repository ppa:libreoffice/ppa && sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install libreoffice-writer

[Mahendra Tallur (mahen)]

Thanks for your message, Christopher.

Indeed, the bug still occurs with LibreOffice 3.3.1 (Ubuntu 10.10, nvidia proprietary drivers).

Cheers !

[Mahendra Tallur (mahen)]

Oops, I overlooked some of your questions.

- The issue occurs with *any* document
- It occurs even with the latest LibreOffice and Ubuntu versions
- It is pretty simple : if an openoffice document is displayed before turning the computer into "sleep" mode, openoffice will be extremely slow (especially scrolling) after waking up the computer. It won't affect documents opened afterwards.

It occurs when Compiz is enabled. I could only test it with Nvidia hardware. (with the proprietary drivers) No other app is affected.

[Harry Bear (hbrazzi-free)]

I confirm this issue occurs with any document open with LibreOffice or Openoffice. It occurs when switching users or resuming...
My config :
- Ubuntu 10.10
- Nvidia proprietary drivers 270.18
- LibreOffice 3.3.1
with compiz activated...

[aldebx (aldebx)]

I can confirm this bug is still present with
- Ubuntu 11.04
- Libreoffice 3.4
- NVIDIA propietary 270.41.06-0ubuntu1
- Compiz 1:0.9.4+bzr20110415-0ubuntu2

after resume from suspend or switching user libreoffice is so slow that is unusable and almost makes the computer freeze.

[penalvch (penalvch)]

Mahendra Tallur, there are no new official OpenOffice.org releases in Ubuntu, as we have transitioned to LibreOffice. => Won't Fix

You are welcome to continue to test and pursue a fix while using LibreOffice. If reproducible in Saucy, could you please execute at a terminal:
apport-collect -p linux 606558

Thank you for your understanding.

[dino99 (9d9)]

That version is no more supported; please open a new bug report if the actual archive found version also has the same issue.