Error message after login: Couldn't connect to accessibility bus
 

Hi all,
few days ago my desktop with Ubuntu 14.04 x86_64 started to send a strange message just after the login (see attached image - sorry but it is in italian). I tried to investigate the reason of the problem and I found that the .xsession-errors file had the following content (translated from italian):
Also the syslog file is reporting strange messages (see attached file)
Finally even the dmesg has errors:
I read on the web that there is a bug about the DBUS, but I didn't understand if there is a fix.

So, any suggestion about how I could try to fix my problem?
Thanks

Claudio

Hi:

I did several searches and I found, just like you that this is a bug.
https://bugs.launchpad.net/ubuntu/+s...s/+bug/1363355

In this thread the member made a change to his rc.conf file. Maybe try it and see if it helps.
https://bbs.archlinux.org/viewtopic.php?id=93840

Update to the most current version of dbus and see if that works.
http://www.freedesktop.org/wiki/Software/dbus/

This member solved the dbus problem by reinstalling his distriubution.
I would put that as the last thing on the to do list.
http://ubuntuforums.org/showthread.php?t=1831509

DBUS session bus needs to write into ~/.dbus (because it is a session bus)
http://www.linuxquestions.org/questi...em-4175420825/

The last article I was able to find is that if 'dbus is owned by root' that can be a possible problem.
http://askubuntu.com/questions/13557...install-or-fix

I hope that helps.-:)

Thanks Ztcoracat for your help.

I've finally solved the problem. I found that the dbus problem was a consequence of the real problem.
The origin of the problem was a usb driver of a peripheral requiring a new compilation after a kernel upgrade. In the past it never required a new compilation, but with one of the last kernel upgrades something has been changed creating an incompatibility with the driver.

So, I can put solved the thread.

Claudio

Your Welcome-

What was the indication that made you suspicious of the driver and compilation or should I say; re-compilation was necessary?

I reviewed the problem from the beginning.
So, I saw that the error was starting just after the login, but the message was saying that there was a problem with password... strange.
Then I tried to access to the system without the graphic, but in this case, just after the login, I received a double request of password from sudo.
At this point I tried to identify what was requiring a root permission to work and finally I identified a script that, after the login, was starting the usb driver of a peripheral.
The idea to rebuild the driver has been suggested me by the VMware virtual machines behavior: every time the kernel changes you have to rebuild it (but in this case it is done automatically).

Basically the error message was saying correctly the place of the problem (the scrpit was located in /etc/profile), but was indicating a wrong reason for the error. This created some confusion instead to help me.

Claudio

Right, I agree.

I see where the error created confusion. Sorry you had to go through that.

Glad that everything is working correctly now.