Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*

This is my fist post, so i could forget something.
Version :
-Version-
Kernel : Linux 4.4.0-34-generic (x86_64)
Compiled : #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
C Library : Unknown
Default C Compiler : GNU C Compiler version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
Distribution : Ubuntu 16.04.1 LTS
Home Directory : /home/stef
Desktop Environment : XFCE 4

This is a installation from scratch.

the same problem occur with GEDIT.

thanks.

Status changed to 'Confirmed' because the bug affects multiple users.

I even encountered this bug when I tried to report it.

$ ubuntu-bug at-spi2-core

** (apport-gtk:####): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-##########: Connection refused

Hello.

I'm having the same problem with mousepad. Yesterday, I've choosed "menu/logout/halt" option instead of "menu/logout/shutdown". And problems started to happen: I could not even reboot or shutdown computer, because every time when I wanted to do this, there was a window to unblock session (I have had to enter my user password and there was not internet connection - it could not be connected via NetworkManager! etc.) The only one working solution to shutdown computer was: press "RESET" and next "POWER" buttons.

I've decided to try shytdown system via shutdown(8) command but it did not work:

[~]$ shutdown now
Failed to power off system via logind: There's already a shutdown or sleep operation in progress

Anyway, there is not LightDM now! I have to login via "unblock" window mentioned above. And when I want to edit some file, there is a WARNING message:

[~]$ mousepad /lib/systemd/system/rtkit-daemon.service

** (mousepad:2869): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*: Connection refused

It happens with every file, that I want to edit etc. Log files contains many entries related to the 'rtkit-daemon'. For example:

rtkit-daemon[1383]: Supervising 0 threads of 0 processes of 1 users.
rtkit-daemon[1383]: Failed to look up client: No such file or directory

I apologize for such a long comment, but mousepad issues, started to happen after described situation. I have no idea if it's important, but it started to happen when I choosed - by accident - 'halt' option instead of 'shutdown' during logout.

Thanks.

Geez, I forgot to write an informations about system version etc. So:

● Release: 16.04 LTS
● Xfce: 4.12.1-3ubuntu1
● Mousepad: 0.4.0-3ubuntu1

Thanks, best regards.

Hello.

Sorry for writing post by post, but there still are problems with Mousepad and 'connecting to accessibility bus' during editing any file. Here is an example:

,----[ $ mousepad /usr/bin/example ]
| ** (mousepad:14099): WARNING **: Couldn't connect to accessibility bus:
| Failed to connect to socket /tmp/dbus-Z3dGTATnQK: Connection refused
`----

Note: the same WARNING message is displayed no matter if 'sudo(8)' command is being used. (However, it seems it is not a rule - if I remember correctly, there wasn't such a message earlier. I mean a couple months ago etc. But I could be wrong.) If it's about release, Mousepad and Xfce4 version informations, everything is the same as above - in my previous post.

By the way: because there is not any reaction on this issue/bug, maybe it should be reported once again, but this time, choosing different 'Affects'? What do you think?

Thanks.

All GTK programs are broken. Same message:
xxxxx@warp:~$ export LANG="ru_RU.UTF-8"; leafpad
(leafpad:18666): dbind-WARNING **: 23:43:20.266: 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.

Launching with sudo or (export NO_AT_BRIDGE=1; leafpad) fix problem:
xxxxx@warp:~$ sudo leafpad
(leafpad:28016): GLib-GIO-CRITICAL **: 00:27:57.489: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

Dbus is running.
xxxxx@warp:~$ echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus
xxxxx@warp:~$ echo $DBUS_SESSION_BUS_PID

(empty string)
========================
This happen after upgrade from 16.04.6 to 18.04.5 (proved on another 2 PC's after upgrade). Kernel 5.4.0-42-generic. I have old kernels and can test with it. PC on MSI P67S motherboard, no suspends, just XscreenSaver.