GNOME Bugzilla – Bug 616261
AT-SPI Registry Wrapper not responding on shutdown
Last modified: 2014-11-13 17:38:07 UTC
When shutting down on Ubuntu Karmic and Lucid, a window pops up saying that the AT-SPI Registry Wrapper is not responding and whether the user would like to force shutdown anyway. This bug is intermittent and does not occur every time. Steps to reproduce: 1. Run Ubuntu Karmic (9.10) or Lucid (10.04) 2. Shutdown the system Expected behaviour: The system shuts down normally. Actual behaviour: A window pops-up indicating that AT-SPI Registry Wrapper is not responding and asking the user whether he wants to force shutdown. See the original bug report in Launchpad: https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/477978
The problem can be reproduced if you have eclipse installed in ubuntu 10.04. You do not need the eclipse package from ubuntu. Download eclipse from http://www.eclipse.org. Try the following steps: 1. launch eclipse from a terminal session. 2. When prompted for the workspace, accept the default. 3. Quit eclipse. Note that although you've left eclipse, the prompt on terminal where eclipse was launched does not appear and you need to press ctrl+c. 4. Shutdown the system A window pops-up indicating that AT-SPI Registry Wrapper is not responding and asking the user whether he wants to force shutdown.
[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.