Re: [Tracker] Cannot retrieve USB storage device UUID using Tracker

[Mihai Stoica <mihai stoica gmail com>]

No I'm sorry for the mistake, it's glib 2.24.2.

On Thu, Oct 14, 2010 at 11:17 AM, Aleksander Morgado <aleksander lanedo com> wrote:

>
>
> I'm using Tracker 0.9.19 in a customized fedora rootfs and I'm trying
> to index a removable etx3 USB Mass Storage device.
> Because automount is disabled I am doing the mount manually in a
> folder visible to tracker.
> The result is as follows:
> (tracker-miner-fs:1418): Tracker-DEBUG: Found 'disk' mounted on path
> '/root/disk'
> (tracker-miner-fs:1418): Tracker-DEBUG:   Using filesystem type:'ext3'
> (tracker-miner-fs:1418): Tracker-DEBUG:   No UUID,
> generated:'0432c965ee57d964ec653dd042c74be7' (based on mount path)
> (tracker-miner-fs:1418): Tracker-DEBUG:   Adding mount point with
> UUID:'0432c965ee57d964ec653dd042c74be7', removable: no, optical: o
> Tracker-Message: Mount point added for URN
> 'urn:nepomuk:datasource:0432c965ee57d964ec653dd042c74be7'
>
>
> On a Ubuntu 10.04 machine I do a similar test with the only difference
> that USB is automounted, I unmount it and then mount it back in home
> folder. In this case the result is:
> (tracker-miner-fs:15960): Tracker-DEBUG: Found 'medias' mounted on
> path '/media/tmp'
> (tracker-miner-fs:15960): Tracker-DEBUG:   Adding mount point with
> UUID:'35788862-be8d-4390-836f-6286bcf1e758', removable: yes, optical:
> no
> Tracker-Message: Mount point added for URN
> 'urn:nepomuk:datasource:35788862-be8d-4390-836f-6286bcf1e758'
> Tracker-Message:   Adding directories in removable/optical media to
> crawler's queue
>
>
> Doing some investigation I've noticed that call to "g_mount_get_volume
> (mount)" from tracker-storage.c is always returning NULL in the
> customized rootfs, so the UUID is always generated and I would really
> need it to be correctly identified in order to avoid indexing twice of
> the same device.
> I can't figure out what is the source of this behavior, what is the
> difference on Ubuntu machine against the customized rootfs. HAL daemon
> is up and running on both, Tracker configuration is the same. A
> difference is that customized rootfs is using systemd and has
> automount disabled.
> Also on fedora rootfs glib is version 2.10-1.
>

Are you using tracker 0.9.19 with glib 2.10? Were you able to compile
it?



--
Aleksander