[Tracker] Tracker - mount device uuid is wrong

[Alexandru Tataru <alexandruflavian gmail com>]

Hello again,

  The situation is like this. When you mount some volume on your host tracker automatically assigns to it a uuid and other general info, like if optical or not, etc. My problem is that on my linux build after I mount a volume tracker says that it could not get the uuid of the new volume and has assigned it's own uuid based on the file path. I took a look at the source code and where the mount fails it says that this situation has never been found, meaning that tracker always finds the volume uuid. Apparently I stumbled upon this situation and I want to know if you can tell me in what situations tracker ca not get the correct uuid for a mounted volume. Because I want the uuid to be always the same and not generated using the volume mounting path.

  Please help!

Have a nice day!