Re: [Tracker] Storage devices not found

[Naa Chetta <sat subscribes gmail com>]

Hi Aleksander,

Thanks for the interesting and informative links. We have a customized distro and the need is to recognize any volume mounts connected/disconnected to the system. The missing glue was the gvfsd in our case. Once I got the daemon running the mounts got identified via tracker.  

Thanks for the support.

Cheers

On Thu, Sep 15, 2011 at 7:00 PM, Aleksander Morgado <aleksander lanedo com> wrote:

Hi hi

(resending to include the list)

>
>
> Nope. We have the gvfs package compiled though. Along with it are
> several other daemons (gvfsd-burn, gvfsd-metadata, etc.) and bins
> (gvfs-mount, gvfs-info, gvfs-ls, etc). These have not been add to the
> image.

Which image are we talking about? MeeGo or some other distro?

> We want to add only the elementary stuff. Could you throw some light
> on what is useful and how would the gvfsd help?
>

See the relevant explanation for this issue in this MeeGo bug report:
https://bugs.meego.com/show_bug.cgi?id=20276#c37

Without gvfsd, GIO will base its GVolumeMonitor on reading /etc/fstab
and the like, and we will get GMounts reported, but not GVolumes.
Tracker needs to have the GVolume information to detect mounts as
removable media. And to get the GVolume information, GIO should base its
GVolumeMonitor on querying gvsfd.

Not sure which is the minimum stuff from gvfsd needed. In this comment
it was suggested that just gvfsd and its direct dependencies were
installed in MeeGo to get it working properly:
https://bugs.meego.com/show_bug.cgi?id=20276#c32

>

> Also, what happens when g_volume_monitor_get_mounts() is called from
> the tracker storage?

We get a list of GMounts. If gvfsd is used as backend in GIO, each of

those GMounts will report a GVolume.

Cheers!

--
Aleksander