Bug 101955 - 64bit JRE not recognized with 64bit LibreOffice
Summary: 64bit JRE not recognized with 64bit LibreOffice
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: grgsmiths
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-07 05:16 UTC by grgsmiths
Modified: 2016-09-08 20:41 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Dbase for review of possible bug in creating Tables (8.41 KB, application/vnd.oasis.opendocument.database)
2016-09-08 16:29 UTC, grgsmiths
Details

Note You need to log in before you can comment on or make changes to this bug.
Description grgsmiths 2016-09-07 05:16:11 UTC
Base 5.2.0.0.4 on Windows 10 64 bit will not work with Java 64 bit or 32 bit... had to load v5.2 of x86 Libre and 32 bit Java to get it working... error message was "LibreOffice requires a Java runtime environment (JRE) to perform this task. 
The selected JRE is defective. 
Please select another version or install a new JRE and select it under 
Tools - Options - LibreOffice - Advanced."

I was hoping to use the new 64 bit LO with Java 64bit... can this be fixed?
Comment 1 Alex Thurgood 2016-09-07 11:26:10 UTC
@grgsmiths : Try using a 64bit JDK instead of a JRE with your 64bit version of LO 5.2.x and report back here.
Comment 2 Alex Thurgood 2016-09-07 11:27:39 UTC
Please also provide us with the Java version you are attempting to use.
Comment 3 Alex Thurgood 2016-09-07 11:28:11 UTC
Oh, and the version of Windows you are using.
Comment 4 grgsmiths 2016-09-07 22:40:15 UTC
ok have JDK 64 bit and LO 5.2.1.2 64 bit running
deleted all else and cleaned registry and rebooted before and after install of above
using Win 10 home 64bit
it works but when in Base I create a table the AutoField will not stay AutoField
when I save it and look at it in edit mode the Field marked as AutoValue yes during creation is now no
and the Field Properties are grayed out so can not set it to yes...
Is this a bug?, or am I doing something wrong?
Comment 5 Robert Großkopf 2016-09-08 05:46:33 UTC
(In reply to grgsmiths from comment #4)
> ok have JDK 64 bit and LO 5.2.1.2 64 bit running
> deleted all else and cleaned registry and rebooted before and after install
> of above
> using Win 10 home 64bit
> it works 

So no bug as described? Status then has to be RESOLVED and WORKSFORME.

> but when in Base I create a table the AutoField will not stay
> AutoField
> when I save it and look at it in edit mode the Field marked as AutoValue yes
> during creation is now no
> and the Field Properties are grayed out so can not set it to yes...
> Is this a bug?, or am I doing something wrong?

This could be a new bug. So please enter a new bug. While reading this I thought: Could it be you have created a Firebird-Database? This type of internal databases is experimental. AutoValue would first work in LO 5.3. Please use HSQLDB instead.
Comment 6 grgsmiths 2016-09-08 16:29:16 UTC
Created attachment 127223 [details]
Dbase for review of possible bug in creating Tables

I have reopened to I assume enable review and response..
Comment 7 grgsmiths 2016-09-08 16:36:47 UTC
I do not see my initial comments so will add them again...
I have been able now to Create tables with the AutoField working...
I have not made any changes to LO... so do not know why it is ok now...
But in case you want to review the Tables still in the dbase I was using, I attached that dbase and reopened this bug report...

Thank you for your comments... I see when I choose to create a dbase that there is a drop down saying HSQLDB Embedded, so I do not know how to create a Firebird-Database...
Comment 8 Alex Thurgood 2016-09-08 17:30:06 UTC
@grgsmiths : unfortunately, that's not how we work in QA.

Your initial problem was solved by installing a 64bit JDK with a 64bit LO, so your bug report must now be set to WORKSFORME, as Robert correctly indicated.

REOPENED is usually only used for bugs that were allegedly fixed by identifiable commits/changes to code, but which didn't in fact work out.

Your second problem, related to a completely different issue, about not getting the AUTOVALUE UI setting to get written to the database, should be made the subject of a separate bug report. It actually kind of rings a bell, maybe I read on one of the mailing lists that someone else had had the same thing (French mailing list mayeb ?). Perhaps a bug report already exists for that.

Closing as RESOLVED WORKSFORME
Comment 9 grgsmiths 2016-09-08 20:41:27 UTC
Ok... will turn in a new bug if I find same issue in future...
but if you want to evaluate the tries I have made at least you have
an attachment of the dbase with tables that have the problem...

Thank you again for commenting and followup