https://bugs.documentfoundation.org/show_bug.cgi?id=163468
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #7 from Michael Weghorn <[email protected]> --- (In reply to Eyal Rozenberg from comment #4) > Understood, but unless this is a known issue, then whatever the problem is > might affect newer versions as well, so it's still worthwhile to try and > figure this out. Sure, but ideally using current versions (which you're doing now) to avoid spending too many resources on issues that might already be fixed and we can't fix for old versions that no longer get updates anyway (unless distros backport fixes, but such issues are not something tracked here, but rather in the distro issue trackers). > I installed these two. The dbind-WARNING is gone; the message about failing > to launch javaldx - remains. To be sure: Do you have libreoffice-java-common installed as well? > It's weird, though: How come the Debian packages don't have those two > packages as dependencies, on one hand - but the libreoffice executables try > and fail to use them, on the other hand? i.e. rely at least partially on > them being available? Technically, you can use LibreOffice (lacking some features then) without Java. For instance, if I force to LO to use a non-existent Java using UNO_JAVA_JFW_JREHOME=file:///tmp/something/invalid libreoffice --writer , I also get a "javaldx failed!" warning, but LibreOffice starts just fine otherwise. I'd expect that Debian uses a "Recommends" on some Java version somewhere in the LO package dependency chain rather than a hard "Depends". (Recommended packages are still installed by default, but it's possible to not have them installed.) It's a bit like not hard-depending on libreoffice-gtk3 or libreoffice-kf5: You can use LibreOffice without these (or just the particular one you're interested in), but if none of them is installed, you'll get the "gen" VCL plugin... In any case, that's a decision of the distro packagers. (In reply to Eyal Rozenberg from comment #5) > Warning: failed to launch javaldx - java may not function correctly > terminate called after throwing an instance of > 'com::sun::star::uno::RuntimeExce > ption' > > ... and it crashes. Does starting with `libreoffice --backtrace` give anything useful, or maybe alternatively `coredumpctl dump` if coredumpctl is in use? Installing the corresponding -dbgsym packages will help getting a more useful backtrace, e.g.: * The backtrace in the initial description shows `/usr/lib/libreoffice/program/libxmlreaderlo.so` * `dpkg -S /usr/lib/libreoffice/program/libxmlreaderlo.so` tells that this file is provided by package `uno-libs-private` * The debug symbols are then provided by a package called `uno-libs-private-dbgsym` -- You are receiving this mail because: You are the assignee for the bug.
