GNOME Bugzilla – Bug 454306
at-spi registry not found error on opening a second session on ubuntu
Last modified: 2014-11-13 14:13:20 UTC
Steps to reproduce: 1. set ubuntu to automatically log into a session where at-spi is enabled 2. from a remote computer, open a new session on the ubuntu machine also with AT enabled; I do it with NX from nomachine.com (of course, the nx-server has to be running on the ubuntu-computer) 3. a message pops up, saying that it could not find the accessibility registry and that the session will be started without assistive technology support. 4. However, if I log out from the automatically opened session (see step1) before logging in remotely with NX, assistive technology also works in the session opened through NX Stack trace: Other information: My ubuntu computer is headless, that is why I am using NX. But I suppose that the problem is not due to nx; I suppose that the problem is rather that it is not possible to run 2 sessions that use Assistive Technology simultaneously.
Created attachment 91306 [details] screenshot of the accessibility registry not found message I already filed the bug some time ago on launchpad; i.e. on the bugtracker of ubuntu https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/117995
Hi Francesco, Confirm. 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. So this is a RFE for us.
Hello Li, Thanks for explaining to me why it does not work in the current release and that it might change in the next release. Francesco
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports. IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
I'm going to go ahead and close this because it concerns a very old version. Feel free to open a new bug if the problem persists.