Apache OpenOffice (AOO) Bugzilla – Issue 7917
Root succeeds, user fails
Last modified: 2003-09-08 16:53:51 UTC
OpenOffice 1.0.1 (downloaded tarball), RedHat 7.3 Intel workstation install, nothing special modified. I successfully did a network install as root, then successfully did workstation installs as both root and a regular user. root is able to run soffice successfully; the normal user is not. When the normal user runs soffice the logo appears, disk grinds for a while, logo disappears, border of a window is drawn but never filled in, then the window disappears and the message "Aborted" is printed on the terminal window. There are a few twists to this story: The regular user is initially able to run the swriter program successfully immediately after the workstation install; however, after he logs out of X and logs in again he is no longer able to run swriter; it fails with the "Aborted" message just like soffice. The regular user is never able to run the soffice program successfully. I found 2 tips in the newsgroups: 1) Verify all fonts are valid; 2) check for write permission on all OpenOffice files in the regular user directory. Red Hat 7.3 uses xfs; initially it was complaining about some erroneous font paths, but I removed them with chkfontpath and now xfs emits no errors. Also I did chmod -R ug+rw OpenOffice.org1.0.1/* in the regular user directory, which should guarantee write access to all OpenOffice files (I also did this for the .sversionrc file). Neither of these suggestions helped anything. I still have the problem of the "Aborted" message when running soffice (and swriter) as the regular user. What is going on? Help!
Thank you for using and supporting OOo. If you are using Gnome as the window manager, please see issue 4494.
Yes, problem is in GNOME. Looking at issue #4494 I tried editing /etc/X11/gdm/gnomerc to say: exec /usr/bin/gnome-session --purge-delay=0 but this did not fix the problem. However, editing soffice to add the command: unset SESSION_MANAGER did fix the problem. So I'm back in business, even if I don't fully understand the issue. Thanks for referring me to the correct issue. After looking at how many duplicate issues there are for this problem, SEEMS LIKE THIS SHOULD BE IN THE FAQ!!!!!!!!!!!! *** This issue has been marked as a duplicate of 4494 ***
DUPLICATE