Issue 30569 - Cannot start OOo
Summary: Cannot start OOo
Status: CLOSED WONT_FIX
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 680m41
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@framework
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2004-06-22 14:17 UTC by lduperval
Modified: 2004-11-25 02:44 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description lduperval 2004-06-22 14:17:30 UTC
I can't start OOo. I can install correctly but when I try to start it, I get a
dialog that says:

The application cannot be started. An internal error occurred.

And that's it.

I'm using GNOME 2.6 on Gentoo.

L
Comment 1 eric.savary 2004-06-22 18:29:17 UTC
Reassigned to framework
Comment 2 Olaf Felka 2004-06-29 13:13:39 UTC
I can't reproduce with 680m45. OOo starts fine.
of @ pj: Are you still using Gentoo? Can you confirm this issue?
Comment 3 peter.junge 2004-06-29 17:24:14 UTC
@OF: Sorry, I did never install Gentoo. Although I'm pretty exited to give it a
try one day it takes too much time in the moment. It's just no normal
distribution but a geeks playgroud ;-) because you build you're very own system
from scratch with only a bit of guidence. Maybe JSK has some experience with it
and I think LLA is a real Geetoo maniac.

--------------------------------------

@lduperval:  Do you have any stack or crash report for us?
Comment 4 lduperval 2004-06-29 23:15:52 UTC
Geeks playground?? Hrmph.

No, I have no stack trace of any sort.

L
Comment 5 Olaf Felka 2004-06-30 09:26:56 UTC
of @ lla: As I have seen in issue 30539 you are using Gentoo. Can you give us
any enlightenment about startup problems of OOo 680? I've never had problems on
Suse, RH or mandrake.
Comment 6 lduperval 2004-06-30 15:44:38 UTC
m45 doen't work for me either. :-(
Comment 7 lars.langhans 2004-07-01 07:31:18 UTC
of @ lla: As I have seen in issue 30539 you are using Gentoo. Can you give us
any enlightenment about startup problems of OOo 680? I've never had problems on
Suse, RH or mandrake.

lla @ of: Yes I'm right firm with Gentoo Linux, ok. I installed an OOo680m45
(lang 49) as normal user only for me (Setup Point, Install OOo 680 for the
current user only), install runs through, start Office see the gree background
screen  try to open a TextDocument, but I can't, all entries are grey :-(
Ok, second try, get important ;-) (with 'su -') and install the same office
version (680m45_49) (Setup point, make OOo 680 available for all users of this
computer) as root, setup runs through, after start I can open a TextDocument
(File->New->TextDocument) I heard that my first point is already known, if not,
ping me please.

lla @ lduperval: Are there exist a .OpenOffice.org680 in your $HOME directory?
If so please rename it and try again with start soffice executable, please. I
know there exist some incompatibilities with older versions.

Regards Lars
BTW:
Gentoo Linux (release 1.4.16 (/etc/gentoo-release)) KDE 3.2.2, Kernel 2.4.26,
glibc 2.3.3
Comment 8 lars.langhans 2004-07-01 08:30:03 UTC
I temporary changed my GUI to Gnome 2.6 and there OOo starts/runs also.
Comment 9 ingenstans 2004-07-01 09:46:09 UTC
I tried m645 using Suse 9.1 and windowmaker, and got exactly this failure: "The 
application cannot be started. An internal error ocurred"

I trieed various reinstalls and repairs. Nothing worked. Booted the machine back 
into Windows, so I can't reproduce it.
Comment 10 Olaf Felka 2004-07-01 13:42:25 UTC
of @ all: For additional help I need detailed walkthrough your installation.
Please give a detailed 'step-by-step'description of your installation process:
user rights (umask), location etc. Did you remove all old .OpenOffice680
directories in your home directory befor starting OOo 680?
Comment 11 lduperval 2004-07-01 14:02:52 UTC
Removing the directory worked. Thanks! I think my problem is that I expected the
installation to work the same way as previous versions of OOO, but it doesn't.
There's no "install" script anymore, just a setup script.
Comment 12 Olaf Felka 2004-07-02 09:01:19 UTC
For every new 680 version the <&home>/.OpenOffice680 directory has to be
removed/renamed first. OOo680 is still in the state of heavy changes and there
is always the chance that some files are getting incompatible from version to
version.
Comment 13 Olaf Felka 2004-07-02 09:02:20 UTC
You might try to keep your old .OpenOffice680 files for a new 680 version. But
on your own risk :-)
Comment 14 niiler 2004-11-25 02:44:48 UTC
I am running VectorLinux 4.3 (a Slackware 9.1 derivative) and I just downloaded
OOo_1.9.m62_native_LinuxIntel_install.tar.gz this evening (2004-11-24).  I
generally use KDE3.3.0.  To install I did the following:

1) tar -xzvf OOo_1.9.m62_native_LinuxIntel_install.tar.gz

2) changed into RPMS directory

3) Used midnight commander to convert rpms to tgz format (I prefer to see
everything I have installed in my /var/log/packages directory and as such don't
ever use rpm)

4) installpkg openoffice*.tgz
   At this point everything installed, but the symbolic links in the
openoffice-core package did not get created (probably because mc screwed up the
conversion).  

5) Just to make sure it wasn't broke, I changed to /opt/openoffice1.9.62/program
and ran (as myself) ./soffice.  This failed to find one of the aforementioned
symbolic links.  So I edited the doinst.sh script that created the links to
actually do it properly. 

6) sudo ./doinst.sh to create symbolic links.

7) Tried running ./soffice again.  This time a small OK-button dialog popped up
saying "The application cannot be started.  An internal error occurred."

8) Trolled the forums for help.  Found a bunch of other slackware users with the
same issue: http://www.oooforum.org/forum/viewtopic.php?t=11992

9) Tried deleting my old OpenOffice.org1.1.2 profile, .sversionrc, and
.OpenOffice.org1.9.62 and rerunning ./soffice.  Note that the new
.OpenOffice.org1.9.62 was not given root permissions and ownership but user and
group permissions and ownership as should be.

10) Logged in as root and tried running ./soffice but with the same results.

11) Logged in as me into IceWM to ensure that it wasn't a KDE thing.  No dice. 
Same results.

12) Tested some other programs.  The following seem to start (which indicates to
me that something small is wrong - we just need to find where):
 spadmin.bin
 testtool.bin
 unopkg.bin
Every other program (swriter, scalc, etc...) seems to die with the same error.

I can provide an strace if necessary.