After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 617727 - When I try using usb-creator-gtk application with my Ubuntu 10.04 system and Orca is running, if I clicking make startup disk button, my desktop accessibility infrastructure is entire blocked
When I try using usb-creator-gtk application with my Ubuntu 10.04 system and ...
Product: at-spi
Classification: Platform
Component: registry
Other Linux
: Normal blocker
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
Depends on:
Reported: 2010-05-05 07:09 UTC by Hammer Attila
Modified: 2014-11-13 18:37 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Hammer Attila 2010-05-05 07:09:25 UTC
Dear Developers,

Because I am a netbook owner, I would like do an USB startup disk with Ubuntu Lucid builtin usb-creator-gtk application. This is a simple GTK frontend application. I using GNOME 2.30 release my Ubuntu 10.04 system.
If Orca Screen Reader is running, and I clicking the make startup disk button, my desktop accessibility infrastructure is entire blocked, only help when I killing X Server with Ctrl+Alt+Backspace key combination. Of course, if Orca is not running when I exiting the screen reader before I clicking the make startup button, usb-creator-gtk application wonderful do the startup disk, but if I try launch Orca Screen Reader when startup disk process is running, the problem is repeated. In Vinux community, sighted users tell me possible happening an at-spi-registry crash, or this is a thread related issue in at-spi. When I try logging out with normal way, my wife see I think at-spi-registry is closed unexpectedly message, but I can not see any crash related data with possible send Ubuntu developers with apport-cli or ubuntu-bug application.
I little sure this is not an Orca bug, because Orca debug.out file not showing any useful information. If you need, I copying what output are see in Orca debug.out file when I clicking the make startup disk button and the startup disk make process is present my screen.

Next comment I insert bugreport links, with I doed this related problem. How can I possible debugging this issue with help you this problem is an at-spi related issue or not?

Comment 1 Hammer Attila 2010-05-05 07:16:42 UTC
I do following bugreports with this related problems:
First, I opened a bug with usb-creator-gtk package in Ubuntu bug tracker:

I opened a bugreport with at-spi package in Ubuntu bug tracker:

This bugreport containing following comment part with Orca debug.out file, possible little help you:
When I try look Orca level debugging what happening when I clicking the make startup disk button and after Orca spokening the cancel button output, I see following lines in remaining entire Orca debug file:
SPEECH OUTPUT: 'Cancel button. Alt c'
^^^^^ PROCESS OBJECT EVENT focus: ^^^^^

---------> QUEUEING EVENT object:children-changed:remove
---------> QUEUEING EVENT object:children-changed:remove
Entire remaining debug.out part containing this me unknown lines. :-(:-(

Comment 2 André Klapper 2010-05-07 10:29:43 UTC
I don't see much sense in filing bug reports all over the place and split related information into several reports as long as it's not clear that this is an upstream issue.

Once somebody states in that it's upstream it makes more sense to go upstream.
Comment 3 André Klapper 2012-02-26 10:43:26 UTC
[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.]
Comment 4 André Klapper 2013-08-14 10:06:27 UTC
[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!]
Comment 5 Magdalen Berns (irc magpie) 2014-11-13 18:37:31 UTC
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.