OpenOffice.org 2.0.2

CrEsPo · 03-22-2006, 08:16 AM

I'm having problems launching OOo 2.0.2. This is what I get when I launch soffice:

Code:

[~]$ soffice
[~]$

If I run OOo 2.0.2 as root it will launch, so it's something with the user settings. I removed the user settings ~/.openoffice.org2 and tried relaunching, but it didn't work.

I'm not getting any error messages in the terminal and the splash screen isn't showing up so I have no idea how to go about this.

Any help is appreciated.

pixellany · 03-22-2006, 09:25 AM

find the openoffice folder and look at the permissions. For the folder and subfolders, execute permissions should be on to all users. In the "program" subfolder, the run scripts (eg soffice, swriter, simpress, etc.) all need to be set so all users have execute permissions.

Here's examples from mine:
From the program folder:
-r-xr-xr-x 1 root root 63 2005-12-14 14:43 swriter
The program folder itself:
drwxr-xr-x 11 root root 20480 2006-03-01 16:42 program

and the top-level folder:
drwxr-xr-x 8 root root 4096 2006-03-01 16:32 openoffice.org2.0

CrEsPo · 03-22-2006, 05:11 PM

Code:

-r-xr-xr-x  1 root root       63 2006-02-23 15:13 swriter
drwxr-xr-x  11 root root  20480 2006-03-22 09:11 program
drwxr-xr-x  8 root root 4096 2006-03-09 14:23 openoffice.org2.0

Thanks for the suggestion, never thought about permissions. The permissions seem correct though, they all have execute permissions. I also noticed they're exactly the same as yours.

pixellany · 03-22-2006, 05:44 PM

Hmmm.....

I just realized---you show the command issued in ~ ---is the openoffice/program directory in your $PATH?

What if you CD into the /xx/xx/openoffice/program directory and run "./soffice" (or "./swriter")??

CrEsPo · 03-22-2006, 06:09 PM

OOo is in my path because it's in /usr/bin which is in my PATH.

Same thing happens if I try it in the program directory.

pixellany · 03-22-2006, 11:21 PM

Quote:

Originally Posted by CrEsPo

OOo is in my path because it's in /usr/bin which is in my PATH.

Same thing happens if I try it in the program directory.

So--in the program directory, you do ./swriter and:
as root, it works
as you, it does not? And--from earlier post, it gives you back a shell prompt--how long before it does this?---ie how long is the command trying to do something before it gives up?

Big HMMMMMMM????

WAIT: Having /usr/bin in your $PATH does NOT mean that /usr/bin/OOo/program is in your $PATH!!!
the PATH variable has to have the absolute path description all the way to the executable file.

But, if you are in the directory doing ./<command>, then PATH is not the issue.

CrEsPo · 03-23-2006, 06:42 AM

Quote:

Originally Posted by pixellany

So--in the program directory, you do ./swriter and:
as root, it works
as you, it does not?

Correct.

Quote:

Originally Posted by pixellany

And--from earlier post, it gives you back a shell prompt--how long before it does this?---ie how long is the command trying to do something before it gives up?

Roughly one second, though sometimes two to three seconds.

Big HMMMMMMM????

Quote:

Originally Posted by pixellany

WAIT: Having /usr/bin in your $PATH does NOT mean that /usr/bin/OOo/program is in your $PATH!!!
the PATH variable has to have the absolute path description all the way to the executable file.

There is a link to soffice in /usr/bin, which is part of my PATH. So it does find the command if I'm not in the program directory of OOo.

Quote:

Originally Posted by pixellany

But, if you are in the directory doing ./<command>, then PATH is not the issue.

Exactly. I can't think of any reason why this is happening. The permissions idea seemed like it would work until I realized they were the same. The thing is I'm getting no error message so I don't know where to start at all.

pixellany · 03-23-2006, 09:08 AM

I'm taking a wild guess that it is a permission issue on some component. I would try doing a duplicate install someplace like /opt

CrEsPo · 03-23-2006, 03:46 PM

Well, I went the cheap way and so far it's working for now. I backed up my home, deleted my account, recreated the account with a UID +1 greater than my old UID and restored my home.

The thing is for the first day OOo worked on my old account, that's why I'm not sure if this fix will stay fixed.

Reason for changing the UID +1 greater was because I heard OOo had some problems with UID and GID's. We'll see how this lays out.