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 641762 - filesystem: cancellation does not always work
filesystem: cancellation does not always work
Status: RESOLVED OBSOLETE
Product: grilo
Classification: Other
Component: plugins
git master
Other Linux
: Normal normal
: ---
Assigned To: grilo-maint
grilo-maint
Depends on:
Blocks:
 
 
Reported: 2011-02-07 18:37 UTC by Guillaume Emont (guijemont)
Modified: 2018-09-24 09:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Guillaume Emont (guijemont) 2011-02-07 18:37:25 UTC
Steps to reproduce:
 * launch grilo-test-ui with GRL_DEBUG=test-ui:debug,filesystem:debug
 * search on filesystem for a string unlikely to be in the name of any file on your file system, such as "kejzalejzalkrez"
 * while it is searching, click on the back button

Expected result (when clicking back):
 * filesystem debugging messages stop appearing
 * a test-ui message appears, and it is similar to the following:
  (lt-grilo-test-ui:9144): Grilo-DEBUG: [test-ui] main.c:661: **** operation finished (2) ****
 * grilo-test-ui stops doing a lot of I/O operations

Observed result:
  * filesystem debugging keeps on displaying messages related to search, showing the operation is still ongoing
  * the test-ui message saying that the operation is finished does not appear, or it does so much later (didn't have the patience to check)
  * grilo-test-ui keeps on doing a lot of I/O operations

Note that it might as well be a bug in grilo-test-ui, I didn't check how it does cancellation.
Comment 1 GNOME Infrastructure Team 2018-09-24 09:15:56 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/grilo/issues/14.