Bug 54644 - Launch of LibO neds long time if JRE is disabled
Summary: Launch of LibO neds long time if JRE is disabled
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.1.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-07 14:31 UTC by m.meinesz
Modified: 2013-07-08 21:21 UTC (History)
2 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 m.meinesz 2012-09-07 14:31:15 UTC
Platform Windows7

I disabled Java RE under OPTIONS->LibreOFFICE->Java

I heard it is not needed any more for browsers, so I thought, that I could disable it on LO as well. However I had a lot of problems then (crashes, very slow start...)

I just want to note, that there should be a warning: Before disabling Java, you need to be warned that this might not be a good idea. 

For all you programmers this might be common sense, but not so for most of your user base.

Thanks for your attention.
Comment 1 Julien Nabet 2012-09-22 10:07:17 UTC
Even if most LibreOffice sources are in C++, there are some parts in Java. Wizards  used in Base are some of these.

Now, we can't do many things here if you don't give detailed examples.
Could you file some crash bugs you have? (by giving the exact steps).

Rainer: about this tracker what do you think about the status it should have?
Comment 2 Rainer Bielefeld Retired 2012-09-23 07:43:49 UTC
Reporter's observations with crashes and slow start art things what have to be fixed. Disabling Java my not cause crashes and may not slow down LibO launch,

I reduced this report to the "very slow start problem"
I a m pretty sure that such a problem has been discussed for more early Versions, butcurrently I can't find that

@m.meinesz: 
"Disabled JRE seems to cause problems" is nothing we can fix. We need something to make this problem reproducible like  "first LibO Launch after PC reboot takes 5s with enabled JRE 1.6.xxx, 15s with disabled JRE. My related settings are Quickstarter disabled, ..., ..." or similar.

Please feel free to submit an additional bug report for your crash problem.
Comment 3 QA Administrators 2013-05-29 23:05:04 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 4 QA Administrators 2013-07-08 21:21:38 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO