[Thunar-dev] ThunarVFS, volumes and pathes

Benedikt Meurer benedikt.meurer at unix-ag.uni-siegen.de
Wed Feb 20 15:23:56 CET 2008

Christophe Chapuis wrote:
> On Wed, Feb 20, 2008 at 9:13 AM, Benedikt Meurer
> <benedikt.meurer at unix-ag.uni-siegen.de> wrote:
>> Christophe Chapuis wrote:
>>  > Well, looks like I've partially found why my problem occurs...
>>  > It looks like when I'm listing all the known volumes and ask for they
>>  > mount path, it returns me pathes like "file:///media/sda1",
>>  > "file:///media/sda2", ..., the volume being mounted or not. Therefore
>>  > I understand that as a consequence
>>  > thunar_vfs_volume_manager_get_volume_by_info doesn't work well.
>>  thunar_vfs_volume_manager_real_get_volume_by_info() iterates only
>>  mounted volumes, see thunar-vfs-volume-manager.c:259.
> Oh, I didn't see that. But this doesn't explain why it doesn't find a
> volume for a local file... which is obviously on a mounted device. So
> I guess I've got a problem with HAL which returns an invalid path, or
> no path at all...
>>  > I don't have any idea where it did take that sort of path, it's not at
>>  > all like that in my fstab, for example.
>>  The paths above are generated by Thunar for volumes where HAL does not
>>  report a path. They will change once HAL reports a valid path (i.e. once
>>  the volume is mounted).
> Well, all of the volumes returned by thunar_vfs where of the form
> "/media/sdaX". For the unmounted one, I understand that it generates
> its own path. But for my root partition, for example, I really don't
> understand: I would expect a path like "file:///". Is it possible that
> my HAL returns an invalid path ?
> Perhaps should I have a different approach ?

Hm, check the HAL properties for the volumes.


More information about the Thunar-dev mailing list