You are not logged in.
Hi,
After upgrade to OO 3.0 it freezes as I try to click anything on the main menu. CPU load rises to 100%; responsible process is soffice.bin.
My /etc/rc.local (somehow I'm not sure it gets executed):
#!/bin/bash
#
# /etc/rc.local: Local multi-user startup script.
#
export OOO_FORCE_DESKTOP=gnome
Tried to do this as root (according to Wiki):
[root@s my]# OOO_FORCE_DESKTOP=gnome soffice
No protocol specified
/opt/openoffice/program/soffice.bin X11 error: Can't open display:
Set DISPLAY environment variable, use -display option
or check permissions of your X-Server
(See "man X" resp. "man xhost" for details)
Any ideas?
Offline
I just upgraded to openoffice-base 3.0.0 and I have the same problem. I renamed my ~/.openoffice2 folder and put "export OOO_FORCE_DESKTOP=gnome" into my ~/.bashrc and echo $OOO_FORCE_DESKTOP gives "gnome" back. As soon as I click a menu, Writer freezes and I need to kill it.
Offline
I am experiencing the same thing, and I think I have tracked the problem down to "export OOO_FORCE_DESKTOP=gnome".
I am using xmonad on an IBM Thinkpad T40 (i686), and prior to upgrading to OpenOffice 3, I did not use any sort of export OOO_FORCE_DESKTOP statement. After upgrading, I added the statement as recommended in the install message. Accessing any menu items in OpenOffice 3 (the open menu, for example), caused 100% cpu usage. So, I downgraded to OpenOffice 2.4.2-1, but had the exact same problem. Removing "export OOO_FORCE_DESKTOP=gnome" from my ~/.bashrc fixed the problem. Unfortunately, OpenOffice 3 won't start without it, so I can't test it there.
Perhaps the problem has to do with a missing dependency related to gnome -- a gtk theme maybe?
$ pacman -Qs theme
local/hicolor-icon-theme 0.10-1
Freedesktop.org Hicolor icon theme
local/tango-icon-theme 0.8.1-1
The Tango Desktop Project exists to create a consistent user experience
local/xcursor-themes 1.0.1-1
X.org Cursor themes
Offline
Removing "export OOO_FORCE_DESKTOP=gnome" from my ~/.bashrc fixed the problem.
In my case, there was no export statement in the first place. I added it in the hope to solve the problem.
Offline
What I'm saying is that OOO 2.4 worked fine (e.g. no cpu spikes) without the export statement, but OOO 2.4 showed the same cpu spikes as OOO 3.0 with the export statement.
Offline
Adding line:
export OOO_FORCE_DESKTOP=gnome
to ~/.bashrc solved my problem.
Cheers!
Offline
I'm having the exactly same problem and no, adding the export statement did not help with the problem.
EDIT: nevermind I forgot to log off
Last edited by Rehto (2008-11-10 18:39:51)
Offline
Ye... don't run apps as root, Billie...
My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...
Offline