Bug 114865 - LO5 and LO5.4.4.2 are packaged in Linux Mint 18.3 Sylvia edition. The 32 bit version download will not allow the user to create an LO5 database. The 64 bit download version has no problems and LO5 Base runs perfectly well.
Summary: LO5 and LO5.4.4.2 are packaged in Linux Mint 18.3 Sylvia edition. The 32 bit ...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.4.4.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-06 17:16 UTC by David Llewellyn
Modified: 2018-01-08 10:17 UTC (History)
0 users

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 David Llewellyn 2018-01-06 17:16:09 UTC
Description:
I downloaded Linux Mint 18.3 Sylvia in late December, just after it was released. I downloaded both the 32 bit and 64 bit versions for two different office equipments, both laptops, one older than the other. Both versions have LO5 and I also upgraded to LO5.4.4.2  With the 64 bit version I can run all packages of LO5 and there is no issue at all. With the 32 bit version, you cannot create a database table at all. If you attempt to create a table, the programme jumps out and returns you to the green Mint screen. All other LO packages run fine - except the Base package. I did mention this to Libre Office during a live chat and was told the "there is a bug in the Java for the 32 bit version" it is not a Libre Office bug.    Can you tell me if by now, after 10 days or so, that the Java bug has been fixed for the 32 bit version, and the LO5.4.4.2 Base package will perform ok in the 32 bit version of Linux Mint 18.3  ??

Actual Results:  
download linux mint 18.3 Sylvia 32 bit distribution
menu
click on Libre Office
click on Libre Office Base
attempt to create a data table

Expected Results:
on clicking the "create table" option, the programme jumps out of Libre Office and returns the user to the green Mint screen. This ONLY happens on the 32 bit download version. I also have the 64 bit download and Libre Office works perfectly correctly in all packages.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Should have allowed me to create tables and a complete database.


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36
Comment 1 MM 2018-01-06 22:43:02 UTC
(In reply to David Llewellyn from comment #0)
I did mention this to Libre
> Office during a live chat and was told the "there is a bug in the Java for
> the 32 bit version" it is not a Libre Office bug.    Can you tell me if by
> now, after 10 days or so, that the Java bug has been fixed for the 32 bit
> version, and the LO5.4.4.2 Base package will perform ok in the 32 bit
> version of Linux Mint 18.3  ??

LO Devs don't fix bugs from Java/OpenJDK. If the bug is in LO then they can fix it 
 else you'll have to wait for the Java/OpenJDK devs to fix it (if they know about the prob.)
Comment 2 Alex Thurgood 2018-01-08 10:17:20 UTC
@David :

Unless you provide information to the contrary this is NOTOURBUG :

1) your report appears to state that the problem occurs with Linux Mint provided versions of LibreOffice - the LibreOffice project is not responsible for packaging decisions made by the maintainers of Linux Mint or the Ubuntu repositories on which the software updates are based. This is not the LibreOffice project's responsibility as both Linux Mint and Ubuntu make their own decisions regarding packaging and version provision.

2) The 32bit Base crash error is, by all reports, linked to a JVM/kernel interaction problem completely independent of LibreOffice. The solution is to update your kernel, or find a kernel patch for your 32bit system that overcomes this problem. A search on the internet in the relevant Ubuntu/Mint forums will indicate how you can attempt to solve this issue. Again, this is not a LibreOffice problem.

For both of the above reasons, marking this report as INVALID. At best, it is NOTOURBUG.