On Tue, 2009-11-10 at 17:14 +0200, Tshepang Lekhonkhobe wrote: > On Tue, Nov 10, 2009 at 17:08, Tshepang Lekhonkhobe<tshep...@gmail.com> wrote:
> > produces a quick crash: > > [snip] > > Tracker-Message: Starting next miner... > > (tracker-miner-fs:23552): Tracker-DEBUG: URN '(null)' (mount point: > > urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66) was not > > reported to be mounted, but now it is, updating state > > (tracker-miner-fs:23552): Tracker-DEBUG: Setting up mount point > > 'urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66' > > Tracker-Message: Crawling recursively directory '/usr/share/applications' > > > > Tracker-CRITICAL **: Could not initialize currently active mount > > points: 1.345: syntax error, undefined variable > > aborting... > > Aborted > > and now with --track-origins=yes, find attached I pushed a fix for this in master. Can you retest this specific use- case? The other problems that you reported in this thread are unrelated to this one. For developers: The set_up_mount_point was not handling URN=NULL correctly, causing the SPARQL query in accumulator to be formatted wrongly. I don't know what we can do in case URN is NULL, so I'm just not handling mount points for devices that have no URN. -- Philip Van Hoof, freelance software developer home: me at pvanhoof dot be gnome: pvanhoof at gnome dot org http://pvanhoof.be/blog http://codeminded.be _______________________________________________ tracker-list mailing list tracker-list@gnome.org http://mail.gnome.org/mailman/listinfo/tracker-list
