LO crashes as soon as I access Help

English
,
#1

Yesterday I upgraded my computers from Fedora 41 to Fedora 42. This brought in LO 25.2.3.1 (X86_64).

After reading the release notes, I wanted to check a few items in the offline help (the corresponding package is correctly installed). Unfortunately, as soon as I Help>LO Help, the application crashes.

If I uninstall the help package, LO spits out a notification telling offline help is not available, as expected, and does not crash.

This happens on all my computers (different CPUs and GPUs) but same OS configuration (Linux 6.14, KDE Plasma).

Before I submit a bug, has anybody experienced this issue and fixed it?

1 Like
#2

Nope. No such issue.

Version: 25.2.3.1 (X86_64) / LibreOffice Community
Build ID: d8d1af5f77df955194e52baabe19324532ac8e8b
CPU threads: 4; OS: Linux 5.15; UI render: Skia/Raster; VCL: x11
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded
#3

Main difference UI render: default; VCL: kf6 (cairo+wayland). I don’t think Wayland may be the culprit because LO (any component) works fine as far as I can tell.

There is no Build ID in Fedora and no alternate UI renderer to “default”.

#4

SAL_USE_VCLPLUGIN=gen libreoffice25.2 starts LO with the generic, built-in UI. I have to use this because Base forms are barely usable with gtk. And no, I can’t reproduce your problem with gtk neither. When I try kf6, it falls back to gtk.

#5

When I force gtk4, LO crashes but there is no “auto-recovery” dialog. Straight, silent crash.

#6

Unnecessary to tell that 25.2.3.1 is still RC?
The 25.2.3.2, also RC, but supposed to get released, is announced for 2025-04-27 (tomorrow).

#7

Thanks @Lupp. Didn’t notice this. My routine is to rely on “production” distro release. If Fedora maintainers made an excessive leap, I’ll wait for stabilisation.

#8

RC versions develop to releases by fixing bugs.
Reporting your issue to bugs.documentfoundation.org might be a good idea.

#9

tdf#166367
Older bug: tdf#165980

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.