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 313104 - When indexing, beagled is stuck, looping on a directory.
When indexing, beagled is stuck, looping on a directory.
Status: RESOLVED WONTFIX
Product: beagle
Classification: Other
Component: General
0.0.x
Other Linux
: Normal major
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2005-08-10 12:17 UTC by Jean-Luc Falcone
Modified: 2006-01-23 21:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jean-Luc Falcone 2005-08-10 12:17:55 UTC 
Please describe the problem:
When indexing, after a few seconds, beagled start looping infinitely on a
directory and do not index anything. The directory where beagled loops is
different on each try.

Here's an example output of beagled --fg --debug:

DEBUG: FileSystemWatcher: OnChangedEvent /home2/falcone/Documents/Images
DEBUG: *** What should we do with /home2/falcone/Documents/Images?
DEBUG: *** Doing nothing to /home2/falcone/Documents/Images
DEBUG: FileSystemWatcher: OnChangedEvent /home2/falcone/Documents/Images
DEBUG: *** What should we do with /home2/falcone/Documents/Images?
DEBUG: *** Doing nothing to /home2/falcone/Documents/Images
DEBUG: FileSystemWatcher: OnChangedEvent /home2/falcone/Documents/Images
DEBUG: *** What should we do with /home2/falcone/Documents/Images?
DEBUG: *** Doing nothing to /home2/falcone/Documents/Images

[... etc forever ...]

Steps to reproduce:
1. Start beagled


Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
Comment 1 manicka 2005-09-09 20:22:10 UTC 
I have the same problem since using gnome 2.12.0 under ubuntu (breezy). 
Everything was fine in 2.11.92 etc
Comment 2 Debajyoti Bera 2005-09-09 21:35:50 UTC 
Correct me if you are wrong:     
You are not using inotify.     
You are using latest CVS (at least one within last 2 weeks).   
  
Can you paste the output of     
$ stat /home2/falcone/Documents/Images    
$ getfattr -d /home2/falcone/Documents/Images   
before starting beagled and again after it has looped a few times.
Comment 3 Joe Shaw 2006-01-04 19:47:23 UTC 
Support for change events without inotify will probably be dropped because it's simply too unreliable.  See http://bugzilla.gnome.org/show_bug.cgi?id=169061
Comment 4 Joe Shaw 2006-01-23 21:08:10 UTC 
Closing this as WONTFIX; the FSW backend have been removed.  Crawling of the filesystem will continue to work, but changes won't be picked up.  inotify is effectively required now.
Comment 5 Joe Shaw 2006-01-23 21:08:37 UTC 
Err, just to clarify: the looping won't happen anymore, but you won't get updates on those files that are changing at all either.