GNOME Bugzilla – Bug 621001
tracker-miner-fs fails to initialize active mount points if CD name has whitespaces
Last modified: 2010-06-15 09:22:15 UTC
If optical media is set to be indexed, and the disk name contains spaces (e.g "Ubuntu 10.04 LTS i386", tracker-miner-fs fails to initialize active mount points as SPARQL update fails: DELETE FROM <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> { <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> tracker:mountPoint ?u } WHERE { ?u a nfo:FileDataObject; nie:url "file:///media/Ubuntu%2010.04%20LTS%20i386" } DROP GRAPH <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> INSERT INTO <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> { <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> a tracker:Volume; tracker:mountPoint ?u } WHERE { ?u a nfo:FileDataObject; nie:url "file:///media/Ubuntu%2010.04%20LTS%20i386" }DELETE FROM <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> { <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> tracker:isMounted ?unknown } WHERE { <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> a tracker:Volume; tracker:isMounted ?unknown } INSERT INTO <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> { <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> a tracker:Volume; tracker:isMounted true } INSERT INTO <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> { ?do tracker:available true } WHERE { ?do nie:dataSource <urn:nepomuk:datasource:Ubuntu 10.04 LTS i386> OPTIONAL { ?do tracker:available ?available } FILTER (!bound(?available)) } Tracker-Critical **: Could not initialize currently active mount points: 1.13: syntax error, expected `:' This is because no UUID can be obtained from the GVolume associated to the mounted CD, so the volume name is used instead as UUID.
Instead of the volume name, which may contain spaces, the MD5 of the volume name can be used. Issue covered in the 'mounts-without-volumes' branch in gnome git: http://git.gnome.org/browse/tracker/commit/?h=mounts-without-volumes&id=4c1beeb97c215104906d94aec81eb1bee95849ab
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.