running libreoffice from command line throws error

[Rob Peters]

At command line enter:

$ libreoffice

(apport-gtk:10403): dbind-WARNING **: 08:19:53.628: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Per Budgie folks, "Looks like the code is assuming gnome shell accessibility is running. This will affect all non gnome shell flavors.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sun Sep 16 08:19:53 2018
InstallationDate: Installed on 2018-09-13 (2 days ago)
InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

[Olivier Tilloy (osomon)]

I cannot reproduce the problem here. I installed the latest Budgie 18.10 iso in a VM and can run libreoffice from the launcher or from a terminal just fine, I'm not seeing that error message.

You didn't specify what happens apart from that error message. Does the application run at all? Does it crash? If so, is there a crash file for it in /var/crash/ ?

[Rob Peters (makitso)]

Strange. I spun up a budgie 18.10 and get the error from the command line. However, libreoffice does start.

[Rob Peters (makitso)]

So, in Libreoffice, I turned off the need for the Java run time environment but still get the error: Warning: failed to read path from javadlx.

[Olivier Tilloy (osomon)]

That java message is harmless, you can safely ignore it.
Was that the error you meant? Because the message in the bug descrition is different.

[Rob Peters (makitso)]

> Was that the error you meant? No it was not. However, using ubuntu 18.10, some system updates seem to have fix the original error.

[Olivier Tilloy (osomon)]

Ok, I'm therefore closing the bug. Feel free to re-open if the issue resurfaces.