[Bug 300443] Re: hal rejects to mount ntfs-3g partition

[Guy Thouret]

After some investigating I found that <match
key="@block.storage_device:storage.hotpluggable" bool="true"> was not
being matched.

If I removed this match key clause, hal-device lists volume.fstype=ntfs-
3g instead of  volume.fstype=ntfs and has the keys with the correct
mount options.

I can now mount the partition as normal by double clicking it's icon,
however I am still asked to authenticate.

I am unsure what effect removing the match key clause will have in other
use cases, this could be left as is and volume.fstype.alternative key
appended within <match key="volume.fstype" string="ntfs"> but outside of
<match key="@block.storage_device:storage.hotpluggable" bool="true">,
but that makes no sense to me to look for an ntfs partition and then add
ntfs-3g to a list of alternatives if the idea is to use ntfs-3g in the
first place.

Note: When I did modify 20-ntfs-3g-policy.fdi to append the
volume.fstype.alternative key I got an error about an invalid mount
object the first time I tried to mount, but it worked the second.

I have attached my /usr/share/hal/fdi/policy/10osvendor/20-ntfs-3g-
policy.fdi

** Attachment added: "20-ntfs-3g-policy.fdi"
   http://launchpadlibrarian.net/20390451/20-ntfs-3g-policy.fdi

-- 
hal rejects to mount ntfs-3g partition
https://bugs.launchpad.net/bugs/300443
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs