[lucid] Impossible make USB startup disk with usb-creator-gtk application, now usb-creator-gtk is unuseable my system

It could be an issue with the CD Drive on the system you are using. Can you try a different (external drive) or perhaps simply point to a .iso image file somewhere and see if the same thing occurs?

Just a moment, I look, but before I doing this, I install upgrades.
But possible this is not CD drive issue, because in Jaunty the startup
disk make works perfect with Lucid CD.
I please maximum 30 minute, and attach the log result what happening
when I try make startup disk from a Lucid iso image.

Attila

I looked with following command in a full updated lucid system:
usb-creator -i lucid-desktop-amd64.iso

I attaching the main window screen shot (usb-creator-gtk.png, the
startup process window screen shot (makestartupdiskprocess.png),
.usb-creator.log, and the final filesyze statistics my USB drive
(copyedfilesize.txt).
If I see right, usb-creator is copyed only 53 MB with about 15 minute.
This is not too small?

My Screen reader is frozen when I click after I click make startup disk
button, I need sighted assistance to make screenshot with process window
after 15 minute, and kill X server.

I hope the attached informations is help you. If need another
informations, I try help.

Attila

In Vinux mailing list, Tony Sales found why happening my problem.
When Orca Screen Reader is running and I click the make startup disk
button, at-spi registri is crash and desktop is unresponsive.

Attila

In Orca Mailing list, I ask hint possible why happening usb-creator-gtk unusable problem when Orca is running after I clicking make startup disk button.
Tom masterson wroted following:
"I have scanned the gtk frontend code and if I am reading it correctly.
THey use separate wrapped threads for the progressbar, retry dialog,
> > failure dialog, and success dialog. I suspect this is the problem we are
> > seeing and I don't know how to test it or let the maintainers know."
Joanmarie Diggs Orca developer says following:
"For any suspect gui changes, you can test by using g_object_idle_add()
(in Python gobject.idle_add())."

I worry this is not an at-spi related issue, because apport-cli does'nt found any crash related data.
When I try debugging Orca level what happening when install progress window is displayed, I see following mistifical line with entire remaining Orca debug file:
---------> QUEUEING EVENT object:children-changed:remove

Attila

This appears to be a threading issue. It occurrs when trying to display the progressbar, failue or success dialogs. to recreate do:
1. Go to a terminal window or use alt-f2 to run a command.
2. Type "sudo usb-creator-gtk"
3. Select appropriate input and output devices.
4. Start the process.

At some point it should lock up. Note that this also happens in Karmic with usb-creator-0.2.7. Also note that it only happens with assistive technology enabled and orca running. Also note that since orca does not normally run for things selected from the admin menu usb-creator should work from there.

It appears to be occurring because of using separate threads to dispaly the above items. Maybe try rearranging the code so that we put the actual work on a separate thread and leave all display stuff on the main thread?

I open a bugreport in Bugzilla the at-spi component with describing this
problem:
https://bugzilla.gnome.org/show_bug.cgi?id=617727

Attila