GNOME Bugzilla – Bug 465103
Desktop objects sometimes have null children
Last modified: 2014-11-14 21:54:29 UTC
I'm going to illustrate this using pyatspi, but I've seen it with the C bindings as well. >>> from pyatspi import * >>> d=Registry.getDesktop(0) >>> for a in d: print a [application | gnome-settings-daemon] [application | gnome-session] [application | gnome-panel] [application | gnome-volume-manager] [application | nautilus] [application | metacity] [application | bluetooth-applet] [application | krb5-auth-dialog] [application | gnome-power-manager] [application | nm-applet] [application | pam-panel-icon] None <=== Lies! [application | puplet] [application | sealert] [application | mugshot] [application | Firefox] [application | wnck-applet] [application | Thunderbird] [application | xchat-gnome] [application | gnome-terminal] I realize that the root of this problem is most likely a buggy application, but after spending literally hours trying to chase down which app is causing this, I'm still empty-handed. It seems like AT-SPI should either provide a useful way to uncover the broken app so we can get it fixed (could be very hard, I don't know), or work around it more gracefully, or both. That would make the life of AT and pseudo-AT developers like myself easier :)
To add to the suspense... >>> for i in range(d.childCount): print d[i] [application | gnome-settings-daemon] [application | gnome-session] [application | gnome-panel] [application | gnome-volume-manager] [application | nautilus] [application | metacity] [application | bluetooth-applet] [application | krb5-auth-dialog] [application | gnome-power-manager] [application | nm-applet] [application | pam-panel-icon] Traceback (most recent call last):
+ Trace 154059
LookupError
:(
*** Bug 441000 has been marked as a duplicate of this bug. ***
I got a crash.
+ Trace 157312
Seems impl_desktop_get_child_at_index return a wrong object for some reason. I think the root causes of the crash and the "NULL" children are same.
I get an ABORT.
+ Trace 171184
*** Bug 488995 has been marked as a duplicate of this bug. ***
[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.