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 569772 - gio.File.copy blocks main loop from *any* thread
gio.File.copy blocks main loop from *any* thread
Status: RESOLVED DUPLICATE of bug 556250
Product: pygobject
Classification: Bindings
Component: gio
Other Linux
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks: 569774
Reported: 2009-01-30 07:08 UTC by John Stowers
Modified: 2009-01-30 17:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Example demonstrating the behaviour (1.85 KB, text/x-python)
2009-01-30 07:10 UTC, John Stowers

Description John Stowers 2009-01-30 07:08:40 UTC

Not sure if this is related to bug #556250 or not, but calling gio.File.copy causes the gtk main loop to be blocked, even if the copy operation is called from another thread.

This makes GIO unusable for Conduit, and is contrary to the behaviour of GnomeVfs.
Comment 1 John Stowers 2009-01-30 07:10:11 UTC
Created attachment 127516 [details]
Example demonstrating the behaviour

This simple app shows copying from a thread causing the main loop to stall.

When copying with GnomeVfs the main loop continues to run (. is printed)
When copying with GIO, the main loop is blocked (no .s are printed)
Comment 2 Paul Pogonyshev 2009-01-30 17:55:07 UTC
Yes, it is the same bug.

*** This bug has been marked as a duplicate of 556250 ***