Bug 40297 - LibO 3.4.3 crashes on startup when extensions offered by default are installed and the OS has Java 7
Summary: LibO 3.4.3 crashes on startup when extensions offered by default are installe...
Status: RESOLVED DUPLICATE of bug 39659
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
3.4.3 RC1
Hardware: x86 (IA32) Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2011-08-22 15:00 UTC by Frédéric Buclin
Modified: 2011-12-26 06:07 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric Buclin 2011-08-22 15:00:59 UTC
I just upgraded my 3.4.1 installation to 3.4.3 rc1 on Windows 7. The installation process went well, but now when I click the soffice.exe icon on the desktop, it crashes while loading extensions. If I reinstall LibO without extensions, it works fine.
Comment 1 Rainer Bielefeld Retired 2011-08-23 00:09:42 UTC
I did not see that problem with "LibreOffice 3.4.3 RC1 - WIN7 Home Premium (64bit) [OOO340m1 (Build:301)]" for upgrade from 3.4.2 and also not for fresh installation.
Comment 2 Jean-Baptiste Faure 2011-08-23 21:00:10 UTC
Hi Frédéric,

Did you try to install LibO with a fresh profile:
- rename your LibreOffice profile
- install LibO 3.4.3 rc1 with extensions

Have you installed LibO in a session with admin rights?

Best regards. JBF
Comment 3 ribotb 2011-08-24 02:34:25 UTC
No problem under my Windows 7 Home SP1.
Maybe a problem with an extension ? Try to start LO with only one different extension each time.

Bernard Ribot.
Comment 4 Frédéric Buclin 2011-08-24 09:43:21 UTC
LibO works fine with the following extensions installed (sorry, names are in french):
- PDF import
- Presentation Minimizer
- Presenter Screen
- Fournisseur de script pour Python

These ones make LibO crash on startup:
- Report Builder
- Fournisseur de script pour JavaScript
- MediaWiki Publisher
- Fournisseur de script pour BeanShell
- Solver de programmation non linéaire
Comment 5 Frédéric Buclin 2011-08-24 09:53:25 UTC
Ah, I found a common point between all broken extensions: they all want Java! I have Java 7 installed, so it may be related to bug 39659. But still, LibO should deactivate the extension if it requires Java but cannot find it. It shouldn't crash.
Comment 6 Frédéric Buclin 2011-08-24 10:27:30 UTC
And FYI, installing Java 6 update 27 fixes the problem. All extensions work fine again and LibO doesn't crash.
Comment 7 Petr Mladek 2011-08-25 05:56:20 UTC
Java 7 currently is not supported. Workaround is "easy" => it should not block the release => lovering the severity a bit.
Comment 8 digital ant 2011-09-06 14:07:50 UTC
I upgraded my 3.4.1 install to 3.4.3 on Windows XP sp3 (32 bit) with no issues. I am running Oracle JRE 6u26. I also removed my App Data\LibO profile before installing (old habits die hard).

App starts and loads extensions with no errors.
Comment 9 Frédéric Buclin 2011-09-25 02:18:58 UTC
(In reply to comment #8)
> I upgraded my 3.4.1 install to 3.4.3 on Windows XP sp3 (32 bit) with no issues.
> I am running Oracle JRE 6u26.

And this bug is about issues with Java 7.
Comment 10 Björn Michaelsen 2011-12-23 12:36:45 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 11 Jean-Baptiste Faure 2011-12-26 06:07:10 UTC
Java 7 recognition problem so duplicate of bug 39659

Best regards. JBF

*** This bug has been marked as a duplicate of bug 39659 ***