LibreOffice hangs on startup

Perfect. That worked for me! Thanks!

Someone please upvote this - FINALLY a solution that worked for me!

Running -

  • /opt/libreoffice6.3/program/soffice
  • — resulted in the splash logo, and the load thermometer hung about 50%
  • /opt/libreoffice6.3/program/soffice --convert-to pdf --outdir /tmp --headless test.odt
  • — Just hung

I renamed the whole : ~/.config/libreoffice/

And both now work fine.

Many thanks, Ian
.

1 Like

Cannot upvote Babak_AB’s comment.
Worked on OpenSUSE Tumbleweed as of 11th of April 2023. I renamed the whole folder, tho

Reset your user profile. See Frequently asked questions - General - The Document Foundation Wiki - important: rename the folder, don’t delete it.

EDIT If that doesn’t help, try a repair install. (Run the install file and choose repair install when that option is offered.)

EDIT 2 You might try to start Windows in safe mode and see if LibreOffice runs then to make sure there isn’t some software conflict.

Maybe there’s a bad registry entry. When you have uninstalled Libre, clean up the Windows Registry - find all instances of Libre that the uninstall didn’t remove and delete them yourself. Then do a re-install.

If this answer helped you, please vote it with :heavy_check_mark: (here on the left). That will help other people with the same question.

Thanks. I did try resetting my profile, but no luck.

I already tried the repair install as well. No luck there either.

I’ll give rebooting in Safe Mode a try - but that seems like a long-shot. I was using LibreOffice perfectly well until one day when nothing worked anymore, and I don’t believe I’ve updated any drivers in-between it working and not working, but who knows?

I did clean the registry after uninstalling, removing all LibreOffice/OpenOffice references, then reinstalling, but that didn’t do the trick. FWIW, I also cleaned out the filesystem as well. But it has to be something like that… :frowning:

It has to be something on your system, because it isn’t crashing on most other computers. Any other system scans? hard disk running fine? I once had trouble with a program that sat on a bad sector on the hard disk.

Sorry for the delay responding. I’ve checked the disk and there’s no bad sectors.

Safe Mode didn’t work, BTW.

Please test replacing your registrymodifications.xcu that is in the root of the user profile, it has the OpenGL disable.

registrymodifications.ods

I have change to extension to ods to upload here, change the extension to xcu after download it.

Thanks for the file. I didn’t replace my own file with the one you provided, because it included a number of settings that weren’t applicable to my machine. But I did copy over the OpenGL related settings (ForceOpenGL and UseOpenGL). Unfortunately, that didn’t do the trick. Do I need any others?

This is a particularly puzzling problem, because I’ve been using LibreOffice (and OpenOffice before that) for many years on this same laptop with no issues whatsoever. Now nothing works… :frowning:

FWIW, the AppData\Roaming\LibreOffice\4\crash directory contains a file called “dump.ini” that contains the following (each time I attempt to run, say, Writer, another identical block is added to the file):

OpenGLVendor=0x8086
OpenGLDevice=0x0126
OpenGLDriver=9.17.10.4229
UseOpenGL=false

That hasn’t changed (I got the same output before adding the OpenGL settings you mentioned to my registrymodifications.xcu file), so I suspect that OpenGL isn’t the problem.

There’s also an AppData\Roaming\LibreOffice\4\cache\opengl_device.log file which contains the following:

DriverVersion: 9.17.10.4229
DriverDate: 5-27-2015
DeviceID: PCI\VEN_8086&DEV_0126&SUBSYS_04941028&REV_09
AdapterVendorID: 0x8086
AdapterDeviceID: 0x0126
AdapterSubsysID: 0x04941028
DeviceKey: System\CurrentControlSet\Control\Video\{469D7B61-9868-45D9-B476-E1C84DBD22BB}\0000
DeviceString: Intel(R) HD Graphics 3000

Hope that helps…

Hi

May be you chan check the registry. See the attachment in tdf#93546

Regards

Thanks for your contribution. I added the specified registry entries - no luck.

These entries basically do the exact same thing that the answer from m.a.riosv suggested in the registrymodifications.xcu file, and they didn’t work either.

I don’t believe that this is an OpenGL-related issue.

In my situation, the problem was related to system proxy settings (it’s set to detect proxy settings automatically). At first, I disable auto detection in system settings. After that LibreOffice starts correctly. Next, I set Proxy server to none in LibreOffice settings and return system settings back.

I have the same problem. Version 7.1.0.3 x64 did install without errors. When trying to start it hung on a ‘final’ splash screen, no errors. I left it for about 8 hours, no changes. After killing the task i then uninstalled it and reinstalled it, same persisting problem. I then tried the 7.0.3 x64 version, same probem, also hung on the final splash screen.

I then tried the 7.0.3 x32 version of Libreoffice. It took a little time, but Writer did start after a about a minute. I noticed some things were setup by Writer after starting it the first time and prior to getting the main Witer window. The second time i started Writer it started quite fast. So there is some sort of post install preparation being done at first time start.

I then started the 7.1.0.3 x64 installer again. It removed parts of the previous 7.0.3 x32 installation and then installed without error. I then started Writer, and it started immediately, no errors, no problems. My best educated guess is that the x64 versions of LibreOffice installer has post installation and pre first time run setup issues which causes LibreOffice to hang on the splash screen.

Other users seem to confirm that the problems seems to be related with the user profile that is being setup by LibreOffice x64. Perhaps my experience can point you to a solution for the x64 installers.

My Windows 10 version is the latest 20H2 version, Build 19042.804, with minimal application setups and all updates applied. Some of the hardware drivers, like for the videocard, are outdated (2016) as this is a HP Pavillion DV7 laptop which has switchable graphics between Intel HD 3000 and AMD Catalyst 15.7. The OpenGL Extension viewer 5.02 reports version 3.1 of OpenGL, the latest 6.18 version simply crashes when querying the Intel HD Graphics 3000 videocard.

So for now, install the x32 version, then upgrade to the x64 version.

1 Like

I would like to thank HCI1 and PeerDragon.

In a machine running Windows 8.1, versions 7.2.1 64 bit and 6.4.6 64 bit would freeze. Version 5.0.0 64 bit always worked and still works normally, but now I have to replace it because I need a new feature in formulas.

I just installed 7.2.1 32 bit, it did not freeze, and so far seems to work perfectly.

Thanks for posting this solution. I also ran into the same problem with LibreOffice 7.x, But the issue started suddenly and persisted through LibreOffice 6.x as well. I tried the above solution by Uninstalling & Re-installing different versions (Both 64 & 32) on Windows10 but with No luck.
I also tried SAFE Mode, disabling the OpenGL, OpenCL as suggested but with No Luck…
AND THEN I THOUGHT OF THE SHARED Printer, since the LibreOffice suddenly started freezing after working fine for months without any hiccups… Once I started UP the Shared Server(with Printer), everything worked fine. It would appear LibreOffice was looking for the printer \IP.address\ —
I then decided set the File → Printer Settings… to “Microsoft Print to PDF” in order to avoid LibreOffice from hanging during startup or opening up documents in the future. I had to Print To PDF in order to persist the changes. The next time LibreOffice started (when the Shared Print Server was offline), all worked well…
I believe LibreOffice has not rectified this even in the newest 7.x version.

My laptop with windows 11 and libreoffice 7.2 would freeze on startup or opening a document and show the message “Loading document…” on the lower left corner, if the default printer was not online. I changed the default printer to an always available one, Microsoft print to PDF, and now I have no more problems.