Comment 4 for bug 115768

I believe we are discussing two different problems here. The error you get is indicative of the absence of polkit, as you correctly observed, and it is an error I get even without ntfs-config (and I thought about reporting it at the time, but eventually forgot about it since i could fix the ntfs-3g automounting as of my first post, and after that it slipped my mind).
This bug report is about the ntfs-config (and supposedly any other) policy file not being parsed under the /etc-based hal policy directory tree. If you move that very same policy file under the /usr/share-based hal policy directory tree, the policy kicks in as soon as you plug the device in, and the ntfs partition gets mounted flawlessly and instantly.

From your output, it looks like you have the ntfs-config policy file under /etc/hal/fdi/policy. What happens if you issue a "sudo mv /etc/hal/fdi/policy/20-ntfs-config-write-policy.fdi /usr/share/hal/fdi/policy/10osvendor" ? On my system, that gets rid of the polkit-related errors, and as i reported in my first post, mounts the partition finely, using the ntfs-3g driver.

nuu