After deletion of ~/.config/libreoffice the loading dialog freezes if I don't start in safe mode and disable hardware acceleration. This issue only occured after I deleted ~/.config/libreoffice and I didn't have to disable hardware acceleration before so I assume that on earlier setups on this device, libreoffice automatically disabled hardware acceleration (because of a different LO version or different graphics drivers. OpenGL version 3.0 Mesa 21.3.9 Amber $ sudo lshw -c video *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:28 memory:f0000000-f03fffff memory:e0000000-efffffff ioport:6000(size=64) memory:c0000-dffff
Could you please follow https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_(_Skia_) ? Considering you seem to have done first steps: - upgrade graphic driver - test with hardware rendering disabled so now we just need skia.log
I believe no skia.log file is created during a such failed attempt to start LO.
Does it freeze too even if you just launch startcenter + avoiding LO splashscreen by typing on a console/terminal: soffice --nologo ? If yes, would it be possible you retrieve a backtrace by following https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU/Linux:_How_to_get_a_backtrace ?
Dear krumelmonster, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Created attachment 191386 [details] backtrace of the frozen libreoffice
Created attachment 191387 [details] trace produced by soffice --backtrace
Hi Julien, Sorry for missing out on your questions. After renaming ~/.config/libreoffice again, again neither `soffice --nologo` nor `libreoffice` bring up a window. The gdbtrace.log produced by `soffice --backtrace` method (with archs debuginfod attached) seemed inconclusive to me so I also created the gdb.txt by attaching gdb to a soffice process intiated by running `libreoffice` and calling backtrace. Let me know if there's any other debug info that may prove useful.
On which Linux distrib are you and with which version? Taking a look at the traces, it seems the pb isn't Skia but OpenCL. Could you apply this part? https://wiki.documentfoundation.org/QA/FirstSteps#Computation-related_issues_in_Calc_(_OpenCL_)
Created attachment 191389 [details] backtrace for libreoffice-fresh 7.6.4-1 (arch linux)
I'm on arch linux. Earlier today that was libreoffice-still-7.5.9-1 from the repositories, I now switched to libreoffice-fresh-7.6.4-1 where I observe the same issues. The backtrace for libreoffice-fresh-7.6.4-1 is attached above. I ran lo in safe mode to get to the configuration dialog. I followed Uncheck Tools ▸ Options... ▸ LibreOffice ▸ OpenCL ▸ Allow use of OpenCL. Restart LibreOffice, check if issue still occurs. after unchecking the option I restarted to normal and the issue persists. Step three was not applicable. "If it does, uncheck Tools ▸ Options... ▸ LibreOffice ▸ OpenCL ▸ Allow use of Software Interpreter (even when OpenCL is not available)." This option is unavailable, presumably because OpenCL is unavailable in safe mode anyways. I was unable to locate a file named opencl_devices.log or opencl_profile.xml anywhere within my home directory or the /tmp directory.
(In reply to krumelmonster from comment #10) > I'm on arch linux. > > Earlier today that was libreoffice-still-7.5.9-1 from the repositories, I > now switched to libreoffice-fresh-7.6.4-1 where I observe the same issues. > The backtrace for libreoffice-fresh-7.6.4-1 is attached above. > Ok, it's indeed related to OpenCL. > I ran lo in safe mode to get to the configuration dialog. I followed > Uncheck Tools ▸ Options... ▸ LibreOffice ▸ OpenCL ▸ Allow use of OpenCL. > Restart LibreOffice, check if issue still occurs. > after unchecking the option I restarted to normal and the issue persists. Ok > > Step three was not applicable. > > "If it does, uncheck Tools ▸ Options... ▸ LibreOffice ▸ OpenCL ▸ Allow use > of Software Interpreter (even when OpenCL is not available)." This option is > unavailable, presumably because OpenCL is unavailable in safe mode anyways. > > I was unable to locate a file named opencl_devices.log or opencl_profile.xml > anywhere within my home directory or the /tmp directory. Could you do these 2 last tests but not in safe mode? (so if unchecking "Allow use of OpenCL" + restart doesn't work as I expect, at least, you may be able to uncheck "Allow use of Software Interpreter..."
In safe mode, only "Allow use of OpenCL" is available as an option in the OpenCL settings and it says "OpenCL is not used". When I turn off safe mode, I can't get to the configuration screen. Is not being able to configure OpenCL in safe an issue on its own?
Ok, I got no other idea then. Can't help here=>uncc myself.
(In reply to krumelmonster from comment #12) > In safe mode, only "Allow use of OpenCL" is available as an option in the > OpenCL settings and it says "OpenCL is not used". When I turn off safe mode, > I can't get to the configuration screen. > > Is not being able to configure OpenCL in safe an issue on its own? You can launch in normal mode, but force disabling OpenCL like this, from a terminal: SAL_DISABLE_OPENCL=1 libreoffice