GNOME Bugzilla – Bug 575273
AT-SPI registry instability
Last modified: 2014-11-14 22:00:08 UTC
Please describe the problem: When running a single test case that intends just to open and close several applications through LDTP, the connection is dropped and the client isn't able to get the list of registered application list any more. Steps to reproduce: 1. Get the list of registered applications 2. Launch an application 3. Get the list of registered applications to find the name of the newly launched application in the AT-SPI registry 4. Get the title of the window based whose parent property matches the name of the application 5. Close the application clicking on the Close or Quit menu. 6. Repeat 1-5 for several applications Actual results: The response received in LDTP client after some time is unable to retrieve application list. Expected results: The test should go through all the desired applications and complete correctly regardless of the number of times that the application list is retrieved. Does this happen every time? Yes, it doesn't happen at the same point; but eventually the test fails because it's not possible to get the list of registered applications. Other information:
I have noticed this too. Guess this is similar lines of http://bugzilla.gnome.org/show_bug.cgi?id=565536#c10 at-spi-registryd misses the information of application at some point
[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!]
*** This bug has been marked as a duplicate of bug 565536 ***