libreoffice in 19.04 not responding on ODT, working on ODS

[Christians]

Libreoffice 6.2.2.2 20(Build:2) hangs on 19.04 with "Loading document.." on ODTs, but not on ODSs. I had no issues on 18.10.

EXPECTED: ODT file opens

WHAT HAPPENS INSTEAD:
* blank LibreOffice 6.2 window opens with brief message "Loading document.."
* when closing the window by clicking on the X a selection box with "force quit" appear. If I click on this right away the mouse freezes. After liberating the mouse with CTRl-ALT-DEL I can click again on force quit and kill the window.
* The problem occurs even when the hidden lock file has been removed.

TROUBLESHOOTING
* Purging libreoffice, reboot, reinstall does not help.
* At first occurrence of the issue, and starting from terminal I got "failed to read path from javaldx", was advised to install java*
* https://askubuntu.com/questions/1138438/libreoffice-file-locking-issues-in-19-04-no-problems-in-18-10

WORKAROUND
Remove /home/myname/.config/libreoffice. But this only works for a short while, and removing the directory must repeated over and over again.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libreoffice-core 1:6.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
Uname: Linux 5.0.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 28 19:26:29 2019
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2019-04-19 (9 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

[Christians (script-vollbio)]

I have since

* purged the 19.04 provided LO version and installed 6.2.3.2 from https://www.libreoffice.org/download/
  sudo dpkg -i *.deb
  sudo apt -y install libreoffice-base //needed for jdk

RESULT: LO is freezing

* purged 6.2.3.2 and went back to standard version

RESULT: LO is freezing

Strange things happen with the software center:
* After "sudo apt purge libreoffice*" LO still appears in the software center and starts from CLI.
* I remove all components from the software center.
* After installing with "sudo apt install libreoffice*", LO does appear in the store as NOT installed.

This is all is very mysterious and frustrating! What else can I test, what log can I check?

Strange things are happening with the Ubuntu software

[Marcus Tomlinson (marcustomlinson)]

Hi Christians, could you check that you don't have the libreoffice snap installed. You can use `snap list` to check. If you do, that would explain libreoffice launching when the debians are uninstalled. You can remove it by calling `snap remove libreoffice`

Once you've removed the snap, try to purge all libreoffice packages again and simply install via `sudo apt install libreoffice` (no asterisk).

[Marcus Tomlinson (marcustomlinson)]

Could you also check that LibreOffice Writer is selected as the default "Open With" application for ODT files.

[Christians (script-vollbio)]

Tks for looking into this guys!
* libreoffice does not appear in snap list
* in Nautilus my right click shows "open with libreoffice writer"

Note that after removing .config/libreoffice opening an ODT works just fine. The locking occurs when I close LO and try to open another ODT.

Adding to the mystery, I noticed that I have several strange extensions installed "Bundled with LibreOffice" :
* canzely-client 0.5.1, claims to be a German assistant for lawyers and adds a German menu to Writer
* Lightproof grammar checker (magyar), points to http://fsf.hu/
* Lightproof grammar checker (Russian)
* lots of LaTex extensions
* Zemberek Turkish Spell Checker

This is bizarre, I have never touched anything Turkish nor Russian.....
I cannot remove the extensions, the lock icon only offers "update".

Note I have no other repositories installed apart from Canonical Partners. This is all pretty crazy. Will my computer lock up and I will have to pay ransom to Germans and Russians?

[Marcus Tomlinson (marcustomlinson)]

Those extensions are a result of installing like this: "sudo apt install libreoffice*". That pulls in all kinds of packages and extensions for libreoffice including the ones you've described.

Please try the following:

sudo apt autoremove --purge libreoffice*
sudo apt install libreoffice

Now when you re-open libreoffice you should not see those extensions anymore. With this clean install, please try reproduce the issue again.

[Christians (script-vollbio)]

Thank You, yes libreoffice* was the reason for my mystery extension install...

But now I cannot remove libreoffice cleanly any longer:

   sudo apt autoremove --purge libreoffice*

    Errors were encountered while processing:
     libreoffice-lightproof-en
     libreoffice-lightproof-hu
     libreoffice-lightproof-ru-ru
    E: Sub-process /usr/bin/dpkg returned an error code (1)

And I cannot remove the extensions on their own:

sudo apt remove libreoffice-lightproof-en libreoffice-lightproof-ru-ru libreoffice-lightproof-hu

       find: ‘/usr/lib/libreoffice/share/extensions/lightproof_ru_RU/pythonpath’: No such file or directory
       dpkg: error processing package libreoffice-lightproof-ru-ru (--remove):

Renewed install claims they are already there:

      sudo apt remove libreoffice-lightproof-en libreoffice-lightproof-ru-ru libreoffice-lightproof-hu
      ...
      libreoffice-lightproof-ru-ru is already the newest version (0.3.4+1.6-1).

lightproof-hu does not show in the extension manager, but I have two others, solver.. and wiki publisher, but cannot break the lock to uninstall them.

And root gives me trouble as well

    sudo libreoffice
    (soffice:30900): IBUS-WARNING **: 17:34:05.008: The owner of /home/myname/.config/ibus/bus is not root!

I had cleaned the cache with sudo apt-get clean.

[Christians (script-vollbio)]

Upon Marcus' advice I installed from snap, and all works great... tks Marcus!

MInor problem: snap does not seem to allow access to /tmp, so other things won't work any longer, for example I cannot open a DOCX mail attachment.

[Marcus Tomlinson (marcustomlinson)]

From the details provided, this issue seems rooted in package misconfiguration. If you can get your packages clean and conflict free again I suspect the problem will go away. Try again:

sudo apt remove libreoffice libreoffice-core libreoffice-common
sudo apt update && sudo apt install libreoffice

Now, it seems the issue of slow opening ODT files is somewhat known: https://forum.openoffice.org/en/forum/viewtopic.php?f=6&t=86605

Could you try creating, saving, and reopening new ODT file and seeing if the same problem occurs. If it doesn't, you could try copying and pasting all of the broken ODT contents into another to see if the new file loads fine.

[Christians (script-vollbio)]

I attach an example of a document that takes 20 secs to load, followed by a cp/paste into a new document that loads very quickly.

[Marcus Tomlinson (marcustomlinson)]

Unfortunately, for me, both files open quickly. Even so, this now seems to be a LibreOffice-specific problem rather than Ubuntu-related.

Could you please file an upstream bug for this slow ODT issue at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided and share the link to that bug here?

It'd be a good idea to attach those files to the report too.

Thanks Christians!

[Christians (script-vollbio)]

Opening with LO 6.2 from the links on this page

   LoadingSlowly_onewordonly.odt takes 25secs with one of eight CPUs maxed out.
   CpPasted_Now loading FAST_LoadingSlowly_onewordonly_.odt takes 1sec

After purging LO 6.2 and installing LO 6.3.0.0.alpha1 both docs load like a flash. Should I still submit a bug against LO for slow loading then?

It seems my package manager is corrupt, as described in #7, and I cannot update the system any longer properly.

    sudo apt-get update && sudo apt-get upgrade

 You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies.
 libreoffice-lightproof-en : Depends: python3-uno (>= 4.0) but it is not installed
                             Depends: libreoffice-core (>= 1:3.5~) but it is not installed
 libreoffice-lightproof-hu : Depends: python3-uno (>= 4.0) but it is not installed
                             Depends: libreoffice-core (>= 1:3.5~) but it is not installed
 libreoffice-lightproof-ru-ru : Depends: python3-uno (>= 4.0) but it is not installed
                                Depends: libreoffice-core (>= 1:3.5~) but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

BUT 'apt --fix-broken install' gets me back to LO version 6.2, which has caused all the trouble. How can I properly clean the package manager?

[Marcus Tomlinson (marcustomlinson)]

Try the following:

sudo rm /var/lib/dpkg/info/libreoffice-lightproof-en.*
sudo rm /var/lib/dpkg/info/libreoffice-lightproof-hu.*
sudo rm /var/lib/dpkg/info/libreoffice-lightproof-ru-ru.*

sudo dpkg --remove --force-remove-reinstreq libreoffice-lightproof-en libreoffice-lightproof-hu libreoffice-lightproof-ru-ru

[Christians (script-vollbio)]

Description:
Most of my ODTs take 25 secs to load in 6.2.3.2., even very small one-word docs.

I have found two WORKAROUNDS:
1) Remove /home/myname/.config/libreoffice, Now the ODT loads fast, but as soon as I close it and re-open it loads very slowly again.
2) If I cp/paste the contents into a fresh ODT, then this loads quickly every time.

The problem disappears in 6.3.0.0.alpha1.

Steps to Reproduce:
1. Load a previously created ODT (example LoadingSlowly_onewordonly.odt, attached).
2. One of my 8 CPUs maxes out, soffice hogs the CPU, and it takes 25 seconds to open.

Actual Results:
ODT takes 25secs to load.

Expected Results:
ODT should load within a second, as it is very small.

Reproducible: Always

User Profile Reset: Yes

OpenGL enabled: Yes

Additional Info:
I had filed this bug https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826757, and it was suggested I submit a follow-up here.

Version: 6.2.3.2
Build ID: 1:6.2.3-0ubuntu0.19.04.1
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3;
Locale: en-GB (en_GB.UTF-8); UI-Language: en-US

[Christians (script-vollbio)]

Created attachment 151571
This ODT takes 25 secs to load in LO 6.2.3.2

[Christians (script-vollbio)]

Created attachment 151572
This ODT is a cp/paste of the contents of the previous attachment, it loads within a second.

[Christians (script-vollbio)]

This #14 fixes my package issues.

The issue with slow loading ODT with LO 6.2.3.2 remains and I have submitted this follow-up https://bugs.documentfoundation.org/show_bug.cgi?id=125426

Note that my problem is fixed when using 6.3.0.0.alpha1. When reverting to 6.2.3.2 the issue re-occurs.

[Marcus Tomlinson (marcustomlinson)]

Thanks for the update Christians. And thank you for the upstream report too.

[Plokklop-z (plokklop-z)]

Unconfirmed on windows 7 x64 with Version: 6.2.3.2 (x64)
Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac
CPU threads: 3; OS: Windows 6.1; UI render: default; VCL: win

[Xiscofauli (xiscofauli)]

it takes 1 second in

Version: 6.3.0.0.alpha1+
Build ID: 33cc1debf963c503636cf9219aa81d1a6cf2e943
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

and

Version: 6.2.5.0.0+
Build ID: 6c3ceaf3e4d59c658d0f9e4e1b22204be25f74e2
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build

[Christians (script-vollbio)]

Works with 6.3.0.0.alpha1+

[Qa-admin-q (qa-admin-q)]

[Automated Action] NeedInfo-To-Unconfirmed

[Xiscofauli (xiscofauli)]

(In reply to Christians from comment #5)
> Works with 6.3.0.0.alpha1+

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.