-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just to check - I get the same error messages with 0.12.3 and

tracker-miner-fs:

27 Sep 2011, 09:44:25: Tracker-Critical **: Could not execute sparql:
8.1: syntax error, expected variable or term

27 Sep 2011, 09:44:25: Tracker-Critical **:   (Sparql buffer) Error in
task 3 of the array-update: 8.1: syntax error, expected variable or ter
m

27 Sep 2011, 09:44:25: Tracker-Critical **: Could not execute sparql:
8.1: syntax error, expected variable or term

27 Sep 2011, 09:44:25: Tracker-Critical **:   (Sparql buffer) Error in
task 4 of the array-update: 8.1: syntax error, expected variable or ter
m

27 Sep 2011, 09:44:25: Tracker-Critical **: Could not execute sparql:
8.1: syntax error, expected variable or term


tracker-store.log:

26 Sep 2011, 13:18:18: GLib-GObject-Critical **: g_object_unref:
assertion `object->ref_count > 0' failed

27 Sep 2011, 09:26:49: GLib-GObject-Critical **: g_object_unref:
assertion `object->ref_count > 0' failed

27 Sep 2011, 09:26:49: GLib-GObject-Critical **: g_object_unref:
assertion `object->ref_count > 0' failed


Is there any progress on this or do you need more info?

Cheers,

Rainer


On 23/09/11 10:20, Rainer M Krug wrote:
> On 23/09/11 10:05, Ivan Frade wrote:
>> Hi!
> 
>> On Thu, Sep 22, 2011 at 11:33 PM, Martyn Russell 
>> <[email protected]> wrote:
>>> On 22/09/11 20:08, Jens Georg wrote:
>>>> 
>>>> On Do, 2011-09-22 at 15:51 +0100, Martyn Russell wrote:
>>>> 
>>>>>> I get these entries into my miner-fs log - is this a 
>>>>>> problem or "by design"?
>>>>>> 
>>> 
>>> I have a feeling this is related to the Region of Interest
>>> work from Ivan which got fixed in 0.12.2 today and 0.10.28. I
>>> have to check though.
> 
>> Hold your horses! :P Those errors are parsing desktop files:
> 
>> 14 Sep 2011, 11:11:44: Tracker-Warning **: Invalid desktop file:
>>  
>> 'file:///usr/share/desktop-directories/X-Unity-All-Applications.directory'
>
>> 
> 
> 14 Sep 2011, 11:11:44: Tracker-Warning **:   Couldn't get name,
>> missing key (Name) 14 Sep 2011, 11:11:45: Tracker-Warning **: 
>> Couldn't properly parse desktop file 
>> 'file:///usr/share/desktop-directories/vmware-ace-vms.directory':
>>  'Desktop file doesn't contain type'
> 
>> My guess here is that after parsing a desktop file we don't
>> check that we have values in the mandatory properites while
>> generating the sparql, then we produce a broken sparql. Can we
>> get one of those .desktop files?
> 
> Attached.
> 
> 
>> Then comes a bunch of dbus errors with the extractor, so probably
>>  tracker-extract is crashing with some files. Would be great if
>> we could either get those files or a backtrace to fix the
>> problem. I wonder if it is related with the EMF format that we
>> don't support. We shouldn't crash or stop processing other things
>> because of that...
> 
> If you tell me how, I can do that.
> 
> 
>> That tracker is also configured to scan everything under /,
>> which is not recommendable. (Is this related with the gvfs bug?)
>> 14 Sep 2011, 18:42:37: Tracker-Warning **: Could not open
>> directory '/tmp/pulse-PKdhtXMmr18n': Permission denied 14 Sep
>> 2011, 18:42:39: Tracker-Warning **: Could not open directory
>> '/var/log/gdm': Permission denied 14 Sep 2011, 18:43:19:
>> Tracker-Warning **: Could not open directory '/proc/12/fdinfo':
>> Permission denied
> 
>> Also, something is wrong with the gstreamer plugins and/or the 
>> mimetypes, because the log says: 09 Sep 2011, 12:43:07: 
>> Tracker-Warning **: Call to gst_discoverer_discover_uri()
>> failed: Your GStreamer installation is missing a plug-in. 09 Sep
>> 2011, 12:44:50: Tracker-Warning **: Call to
>> gst_discoverer_discover_uri() failed: This appears to be a text
>> file
> 
> Any idea what?
> 
> 
>> And your PDFs doesn't work fine with poppler: 9 Sep 2011,
>> 14:53:32: Tracker-Warning **: Couldn't create PopplerDocument
>> from uri:'file:///home/rkrug/Documents/xxxxxxxx.pdf', PDF
>> document is damaged
> 
> 
> 
> 
>> Next step is to get those problematic .desktop files, ping the 
>> maintainers to fix them ;) and make our parser more robust. Then 
>> fix the extraction for those problematic files. We can use 
>> http://filetea.me to share them.
> 
> OK - I attached the desktop files,
> 
> some (really damaged!) pdfs are here:
> 
> https://filetea.me/t1sbc111 https://filetea.me/t1sc30b9 
> https://filetea.me/t1sc1e02
> 
> Hope this helps,
> 
> Rainer
> 
> 
> 
>> Regards,
> 
>> Ivan _______________________________________________
>> tracker-list mailing list [email protected] 
>> http://mail.gnome.org/mailman/listinfo/tracker-list
> 
> 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      [email protected]

Skype:      RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6BgPwACgkQoYgNqgF2egqsXwCeKGI6sVR/JQogUy3NUYo34KhD
us4AoIXbfLuLsLked16RFzsqaHxemXkH
=zi7x
-----END PGP SIGNATURE-----
_______________________________________________
tracker-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/tracker-list

Reply via email to