Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SO 5.2 Abort problem

1 view
Skip to first unread message

Czouch

unread,
May 31, 2004, 2:47:36 PM5/31/04
to
Hello,
I am trying to install StarOffice 5.2 on my RedHat 8.0 system.
The installation, done with the /net switch as root, seems to work
fine. When I run the program as a regular user, however, it says
"Abort" and will not run.

Can anyone help?

Thanks!

Matthew

Atro Tossavainen

unread,
Jun 1, 2004, 6:38:26 AM6/1/04
to
matt...@netzero.net (Czouch) writes:

> Can anyone help?

Do you read the replies?

--
Atro Tossavainen (Mr.) / The Institute of Biotechnology at
Systems Analyst, Techno-Amish & / the University of Helsinki, Finland,
+358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own.
< URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS

Czouch

unread,
Jun 1, 2004, 10:53:13 PM6/1/04
to
> Do you read the replies?

I'm sorry, but for some reason, a full day after I posted the original
message, I still couldn't see it, so I thought it got lost and decided
to repost it.

I don't have StarOffice 6.0 or 7.0. I have StarOffice 5.2 on CD-ROM,
and I don't have the bandwidth to download the newer versions. Also,
my machine is a lowly 200 MMX with 64 MB RAM. I have a feeling the
newer versions might run too slowly. I already have that problem with
OpenOffice, which is why I decided to go back to StarOffice 5.2.

Matthew

Atro Tossavainen

unread,
Jun 2, 2004, 3:49:52 AM6/2/04
to
matt...@netzero.net (Czouch) writes:

> I don't have StarOffice 6.0 or 7.0. I have StarOffice 5.2 on CD-ROM,
> and I don't have the bandwidth to download the newer versions. Also,
> my machine is a lowly 200 MMX with 64 MB RAM. I have a feeling the
> newer versions might run too slowly. I already have that problem with
> OpenOffice, which is why I decided to go back to StarOffice 5.2.

I see.

You may be able to find out what the problem is by tracing the program
execution. Do a "strace -o /tmp/somefile soffice". When soffice has
failed, the "somefile" will contain a log of all system calls that the
program performed and, hopefully, clues to why it failed. Start
looking at the file at its end, there will be a very large amount of
useless garbage in the beginning.

Czouch

unread,
Jun 3, 2004, 4:15:39 PM6/3/04
to
Atro Tossavainen <Atro.Tossa...@helsinki.finland.invalid> wrote in message news:<pgz8yf6...@kruuna.Helsinki.FI>...

>
> You may be able to find out what the problem is by tracing the program
> execution. Do a "strace -o /tmp/somefile soffice".

Well, I'm not quite sure what happened, but simply by running this
command you suggested, it fixed it. At right about the time it had
been crashing, there was a slight flicker of the splash screen, and
then it launched as normal. It's been working fine since.

Thank you!

Matthew

Atro Tossavainen

unread,
Jun 9, 2004, 5:47:46 AM6/9/04
to
matt...@netzero.net (Czouch) writes:

> Well, I'm not quite sure what happened, but simply by running this
> command you suggested, it fixed it. At right about the time it had
> been crashing, there was a slight flicker of the splash screen, and
> then it launched as normal. It's been working fine since.

That's even weirder.

0 new messages