https://bugs.documentfoundation.org/show_bug.cgi?id=163468
--- Comment #4 from Eyal Rozenberg <[email protected]> --- (In reply to Michael Weghorn from comment #3) > OK, "really old" may be relative, but the version has been out of (upstream) > support for more than a year by now. 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. > I don't know Q4OS myself, but according to their website, it's Debian-based > and [1] suggests that the current version is based on Debian 12 (bookworm), > so you might try installing LO 24.8 from the Debian backports repository: I'll try that first and report. > Building e.g. in a 32-bit chroot of the distro on a 64-bit system could be > another option, but requires some more effort. > If not installed yet, installing a JRE/JDK might fix this warning, e.g. > package openjdk-17-jdk in Debian bookworm. (Or just the runtime, i.e. > openjdk-17-jre should be enough, I guess.) > > > (soffice:14008): dbind-WARNING **: 16:53:58.636: AT-SPI: Error retrieving > > access > > ibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name > > org.a11 > > y.Bus was not provided by any .service files > > On Debian, package at-spi2-core would provide the corresponding file: > /usr/share/dbus-1/services/org.a11y.Bus.service I installed these two. The dbind-WARNING is gone; the message about failing to launch javaldx - remains. 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? > From looking at the backtrace, I'm not sure whether the above 2 warnings are > really related to the actual crash, though. But it's always good to rule out > other problems that may or may not be related. So, we've removed those potential causes, but the conundrum remains. Will try using the 32-bit Debian packages. -- You are receiving this mail because: You are the assignee for the bug.
