LibreOffice 5.4 hangs on start

Hello to all,

LibreOffice 5.4 is hanging on my Tumbleweed box. I’ve been on tihs OS only a few months, but long years on Linux. A little googling suggested starting in --safe-mode…didn’t help. Removing “user” folder from .config/libreoffice/4…that didn’t work either. Removing “registrymodifications.xcu” file from “user”…didn’t work either.

The app starts, creates the generic splash screen, the loading bar appears at the bottom of the splash and starts moving to the right, but hangs after only 10-20% progress. Task Manager shows 100 MB or so of memory used, but 0% CPU.

Anybody got any thoughts?

thanks and happy weekend.

Dave

Does this happen for a newly created fresh user? Or what happens if you rename ~/.config/libreoffice? Those to rule out it’s something in your config
How do you update TW? Should be


zypper dup --no-allow-vendor-change

If you start it from a terminal window, does it say anything?

Thanks, but none of these helps.

  1. I do update via zypper dup --no-allow etc…
  2. starting from a terminal via “libreoffice --safe-mode” doesn’t do anything
  3. “moving/renaming” .config/libreoffice/4/user to “olduser” does nothing…the app starts long enough to create a new “user” folder, then hangs
  4. “moving/renaming” .config/libreoffice/4/user/registrymodifications.xcu to “oldregistrymodifications.xcu” and restarting also does nothing…the app launches and hangs after creating a new copy of registrymodifications.xcu.

I have not tried creating a whole new system user via adduser…not a bad idea. Any thoughts on particular switches to use, or just a plain old “vanilla” user?

thanks and regards

Easiest to create user in Yast it does all the little things for you

Just FYI, this is what I have installed resulting in a working LibreOffice:


@knurphtlaptop:~> rpm -qa | grep -i libreoffice
libreoffice-writer-5.4.0.0.beta2-1.1.x86_64
libreoffice-5.4.0.0.beta2-1.1.x86_64
libreoffice-filters-optional-5.4.0.0.beta2-1.1.x86_64
libreoffice-math-5.4.0.0.beta2-1.1.x86_64
libreoffice-gnome-5.4.0.0.beta2-1.1.x86_64
libreoffice-share-linker-1-4.1.noarch
libreoffice-icon-theme-breeze-5.4.0.0.beta2-1.1.noarch
libreoffice-l10n-en-5.4.0.0.beta2-1.1.noarch
libreoffice-l10n-nl-5.4.0.0.beta2-1.1.noarch
libreoffice-base-drivers-mysql-5.4.0.0.beta2-1.1.x86_64
libreoffice-kde4-5.4.0.0.beta2-1.1.x86_64
libreoffice-impress-5.4.0.0.beta2-1.1.x86_64
libreoffice-gtk3-5.4.0.0.beta2-1.1.x86_64
libreoffice-icon-theme-hicontrast-5.4.0.0.beta2-1.1.noarch
libreoffice-base-5.4.0.0.beta2-1.1.x86_64
libreoffice-pyuno-5.4.0.0.beta2-1.1.x86_64
libreoffice-icon-theme-galaxy-5.4.0.0.beta2-1.1.noarch
libreoffice-icon-theme-tango-5.4.0.0.beta2-1.1.noarch
libreoffice-calc-extensions-5.4.0.0.beta2-1.1.x86_64
libreoffice-draw-5.4.0.0.beta2-1.1.x86_64
libreoffice-writer-extensions-5.4.0.0.beta2-1.1.x86_64
libreoffice-icon-theme-sifr-5.4.0.0.beta2-1.1.noarch
libreoffice-calc-5.4.0.0.beta2-1.1.x86_64
libreoffice-branding-upstream-5.4.0.0.beta2-1.1.noarch
libreoffice-mailmerge-5.4.0.0.beta2-1.1.x86_64
libreofficekit-5.4.0.0.beta2-1.1.x86_64

just to rule out missing packages.

I’m just going to give my test user a try, created with YAST as suggested. But my installation looks almost the same as yours…no nl file of course (maar ik kan een beetje van Uw taal. :wink: ) you have the libreofficekit file that I don’t…oh hell, here:


david@localhost:~> rpm -qa | grep -i libreoffice
libreoffice-base-5.4.0.0.beta2-1.1.x86_64
libreoffice-mailmerge-5.4.0.0.beta2-1.1.x86_64
libreoffice-math-5.4.0.0.beta2-1.1.x86_64
libreoffice-icon-theme-hicontrast-5.4.0.0.beta2-1.1.noarch
libreoffice-draw-5.4.0.0.beta2-1.1.x86_64
libreoffice-base-drivers-mysql-5.4.0.0.beta2-1.1.x86_64
libreoffice-branding-upstream-5.4.0.0.beta2-1.1.noarch
libreoffice-icon-theme-galaxy-5.4.0.0.beta2-1.1.noarch
libreoffice-icon-theme-sifr-5.4.0.0.beta2-1.1.noarch
libreoffice-pyuno-5.4.0.0.beta2-1.1.x86_64
libreoffice-gnome-5.4.0.0.beta2-1.1.x86_64
libreoffice-calc-5.4.0.0.beta2-1.1.x86_64
libreoffice-writer-5.4.0.0.beta2-1.1.x86_64
libreoffice-share-linker-1-4.1.noarch
libreoffice-writer-extensions-5.4.0.0.beta2-1.1.x86_64
libreoffice-impress-5.4.0.0.beta2-1.1.x86_64
libreoffice-icon-theme-breeze-5.4.0.0.beta2-1.1.noarch
libreoffice-5.4.0.0.beta2-1.1.x86_64
libreoffice-calc-extensions-5.4.0.0.beta2-1.1.x86_64
libreoffice-l10n-en-5.4.0.0.beta2-1.1.noarch
libreoffice-filters-optional-5.4.0.0.beta2-1.1.x86_64


nothing glaringly absent…I use Xfce as my desktop, so no kde file, of course.

tot ziens

OK, some progress. I went into my “testman” user, and LO started up with no issues at all. The registrymodifications.xcu file was 87 lines long. In my .config in my regular user, that file only has seven lines. So that seems to be the problem…or at least a symptom of it. Unfortunately, it looks more a symptom…when I delete everything in .config/libreoffice/4 so there is neither a user folder or the old, renamed “olduser” folder…nothing at all…and then start LO, you’d think I’d get a new user folder with new, default registrymodifications file in it…but I don’t. I get the same, truncated, seven line file that was in the old corrupted folders.

So, what writes registrymodifiications.scu, and why can it do it correctly in the test user’s case but not my regular user?!

thanks and regards,

Dave

PS…can I really not upload an image file from my HDD…insert image wants a URL, doesn’t accept this path?

/home/david/pictures/Screenshot_LibreOff-splash_in_window.png

You can, on https://paste.opensuse.org . On top, click Image, the rest speaks for itself. It gives a link.
Or use a free imagehoster, that provides forums code like imagebam or the like.

What happens if you copy over the ~./config/libreoffice folder from the new user, as root, then change ownership to you user, also as root, then start

All good now, working again. I did cp and chown as you suggested, and everything looked OK, but still hung in exactly the same old bad way as before. Then, almost by accident, I did an “ls -al” instead of “ls -l” and there was a .lock file hanging around that I couldn’t account for. So, I got it out of there and restarted, and all was well.

thanks for your quick response and good suggestions.

regards