You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2012/05/19 00:33:57 UTC

[Bug 119377] OO 3.4 Fails to Start - User must select a JRE from options dialog!Application Error Fatal exception: Signal 6

https://issues.apache.org/ooo/show_bug.cgi?id=119377

Ariel Constenla-Haile <ar...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |arielch@apache.org

--- Comment #1 from Ariel Constenla-Haile <ar...@apache.org> ---
(In reply to comment #0)
> OS: openSuSE 11.4 x86_64. Replaced the OpenOffice 3.3 install with new 3.4
> install. 

Did you remove every OpenOffice.org package *before*?
Unfortunately, you cannot update from OpenOffice.org to Apache OpenOffice, you
have to remove every OOo package before, and make sure that in /opt/ there are
no folders remaining.


> Installed via
> Apache_OpenOffice_incubating_3.4.0_Linux_x86-64_install-rpm_en-US.tar.gz
> with cd ../RPMS && rpm -Uvh *.rpm
> 
> After install, attempting to start openoffice (any module) results in the
> following:
> 
> 14:39 alchemy:~> /opt/openoffice.org3/program/soffice
> javaldx failed. User must select a JRE from options dialog!

This is just a warning.

This is the error, and is the typical error that has been seen when AOO is
installed as an update to OOo:

> Application Error
> 
> Fatal exception: Signal 6
> Stack:
> /opt/openoffice.org3/program/../basis-link/ure-link/lib/libuno_sal.so.
> 3(+0x34f5b)[0x7fc24ea33f5b]

[...]


> This shouldn't occur in a default install. What can we do to work around
> this issue or fix it?  Let me know if I can send you anything else. Thanks.

Please try removing every OOo package before (including the desktop
integration).
Make sure you don't have any openoffie.org* folder in /opt/ before attempting
to install AOO.

-- 
You are receiving this mail because:
You are on the CC list for the bug.