Libreoffice doesn't starts on kubuntu 18.04 32bit

Bug #1760998 reported by Alessandro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Any time I try to run any libreoffice package I can see just the loader image, starts loading and than crash

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice 1:6.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic i686
ApportVersion: 2.20.9-0ubuntu2
Architecture: i386
CurrentDesktop: KDE
Date: Tue Apr 3 23:43:48 2018
InstallationDate: Installed on 2018-03-28 (6 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.9-0ubuntu2
Architecture: i386
CurrentDesktop: KDE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-03-28 (6 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
Package: libreoffice 1:6.0.2-0ubuntu1
PackageArchitecture: i386
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Tags: bionic
Uname: Linux 4.15.0-13-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Alessandro (alex-kubu) wrote :
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1760998

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in libreoffice (Ubuntu):
status: New → Incomplete
Revision history for this message
Alessandro (alex-kubu) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Alessandro (alex-kubu) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Alessandro (alex-kubu) wrote : ProcEnviron.txt

apport information

Revision history for this message
Olivier Tilloy (osomon) wrote :

This is most likely a duplicate of bug #1726145 (which itself is bug #1699772).

What's the output of

    grep enabled ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml

If it looks like:

    <enabled xsi:nil="true"/>

Can you edit that file with a text editor and change it to:

    <enabled xsi:nil="false">false</enabled>

And see if that makes the crash go away?

Revision history for this message
Alessandro (alex-kubu) wrote :

I tried to change the configuration file of libreoffice as suggested and something is changed, now it appears a message saying something like "Libreoffice need JRE to run" and offers me the button to start it, but when I try to start it nothing happens and the same message comes back.

After that I check again the config file and I saw that it's changed. The modified line that was:

<enabled xsi:nil="false">false</enabled>

became like :

<enabled xsi:nil="false">true</enabled>

Anyway, Libreoffice doesn't starts yet

Revision history for this message
Olivier Tilloy (osomon) wrote :

Which application of the libreoffice suite did you run? The only one that strictly requires a JRE that I'm aware of is base (for databases).

Can you copy verbatim the exact message that is displayed saying it requires a JRE to run?

Revision history for this message
Alessandro (alex-kubu) wrote :

I tried to run the main libreoffice but now trying to run libreoffice --writer the same message appears ( see the attachment ).

Like I said is an Italian message and it asks to re-enable the JRE, doing it another message comes out, asking to restarts Libreoffice, but clicking the button to restart Libreoffice the second message disappears for a moment and than come back.

Revision history for this message
Olivier Tilloy (osomon) wrote :

What happens if you answer "No" to the first message? Does the application start (with the JRE disabled)?

Revision history for this message
Alessandro (alex-kubu) wrote :

If I answer "No", that message keep to come back.

To be more precise, I get this message just when I modify the libreoffice config as suggested but if I answer "Si" (yes) and second message appear, like I said the config file will be change, like explained before, and until I modify the config again, trying to start any libreoffice app has the same result, just the splash and than disappear, without error o messages.

Revision history for this message
Olivier Tilloy (osomon) wrote :

And what happens if you click "Annulla" after restarting the application after modifying the config file to disable the JRE ?

Something else to try: run the application with the --safe-mode parameter:

    libreoffice --safe-mode

Revision history for this message
Alessandro (alex-kubu) wrote :

something really not understandable to me has happened.

I tried to open Writer and clicking "annulla" nothing was happening and same message was coming back, after about 10 time clicking "annulla" the application appears and as well the same message as before, at this point clicking again "annulla it disappears", but when I close the app, the same message come back again and to close it I click "annulla" 2 times.

Opening libreoffice with "libreoffice --safe-mode" the main app is showed with another window to reset any settings and after doing so it seems to work normally.

After that any application of the libreoffice suite seems to works as aspected.

Should I consider the problem solved !?!

Revision history for this message
Olivier Tilloy (osomon) wrote :

Glad this is finally working for you!

It looks like running "libreoffice --safe-mode" allowed you to reset your profile to a working state, with the JRE really disabled. Not sure why changing the setting manually in javasettings_Linux_*.xml was not enough.

Per comment #6, I'm marking this bug a duplicate of bug #1726145.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.