at-spi registry not found when in second session

Bug #117995 reported by Francesco Fumanti
4
Affects Status Importance Assigned to Milestone
at-spi
Expired
Wishlist
at-spi (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu is installed on a remote headless machine that is configured to automatically login into a session with administrative rights.

When I connect to the remote ubuntu machine by using vnc, everything seems to work as expected. As applications requiring at-spi work, I suppose that at-spi is also running as it should.

When I connect to the remote ubuntu computer by usung nx, as soon as the nx-client window opens, I get a dialogue telling me that the accessibility registry has not been found and that the session has been started without assistive technology support. Only after dismissing the dialogue does the desktop appear.

I tried removing the NX packages and reinstalling them, but the problem persist. It occurs every time that I open a session through NX and applications requiring at-spi do not work.

Could it be that it does not work in NX because it is already running in the session automatically started after booting?

at-spi version 1.18.1-0ubuntu1
nxclient_2.1.0-17_i386.deb
nxnode_2.1.0-22_i386.deb
nxserver_2.1.0-22_i386.deb

I will attach the output of demsg, lspci vv and lspci vvn to this thread.

Moreover, don't hesitate to contact me if you need more info.

Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Francesco Fumanti (frafu) wrote :

My previous assumption was not completely correct: it seems that nx is not the problem. In fact:

If I log out of the automatically opened session with vnc before I try to connect with nx, at-spi works fine in the nx session. Consequently, I now wonder whether the problem is not that at-spi does not start in a new session when it is already running in another session.

PS: I have edited the title of the bug accordingly.

Changed in at-spi:
status: Unknown → In Progress
Revision history for this message
Luke Yelavich (themuso) wrote :

With the second manually started session, are you also running as root, i.e are both session s running as root? If so, it seems quite obvious that at-spi doesn't work, as its already running for the same user in another session.

Revision history for this message
Francesco Fumanti (frafu) wrote :

I don't know exactly what you mean with root, but I can confirm that I used the sameuser name in both session, username that can get admin privileges with sudo/gksu.

By the way, Li Yuan already commented in the corresponding upstream bug (linked above), that the at-spi-registryd can not be started twice for the same user; he also explains why.

Revision history for this message
Raphaël F. (rflores) wrote :
Revision history for this message
Raphaël F. (rflores) wrote :

Hello,

I have the same problem since I've made my session login automatically. The problem does not seem having a link with vnc or nx tools.

The same windows appears at the left top corner and the sessions waits me to validate the error message before loading Gnome and others...

I've put the result of aptitude show at-spi juste below, if it can help in the resolutino of the problem...

Thanks.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Current version (at-spi): 1.26.0-0ubuntu2

Changed in at-spi (Ubuntu):
status: New → Incomplete
Revision history for this message
Francesco Fumanti (frafu) wrote :

I just tried on Ubuntu Jaunty and I don't get the error message anymore.

However, mousetweaks that requires at-spi does not work in the nx session. On the other hand, gok seems to work. So I don't know whether the problem has been really solved.

The following quote taken from the 8th August 2007 from the corresponding upstream bug might be relevant:

"Currently we don't support starting two at-spi-registryd under one
user. Because we still need to register as a bonobo server when startup, some
python ATs are still get registryd by bonobo. I think we can get rid of bonobo
in the next release. They can get registryd IOR from X root window."

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in at-spi (Ubuntu):
status: Incomplete → Invalid
Changed in at-spi:
importance: Unknown → Wishlist
Changed in at-spi:
status: In Progress → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.