auto mount does not correctly assigns permissions even permissions says "rw-------" I can not create any file or folder, or delete files. It seems devicekit is not aware of ntfs-3g. it mount with kernel ntfs driver. my setting in gconf for ntfs-3g is working for non-devicekit setup as uid, dmask, fmask are correctly set with normal setup. Reproducible: Always Steps to Reproduce: 1.emerge devicekit and gnome-panel 2.insert a flash disk with ntfs 3.try to create file on usb disk Actual Results: Filesystem is mounted with kernel ntfs driver Expected Results: devicekit respects gconf and mounts disk with ntfs-3g Mounting disks with gnome-mount works as intended while automount is not working with devicekit.
sorry for wrong description, gvfs should be compiled with gdu USE flag to see this effect. There are debian bugs about this issue. I will report if the solutions will work or not
There is several bug reports against devicekit-disks issues. Here are summaries: 1. If ntfs-3g will be used as a default, then there should exists /sbin/mount.ntfs symlinked to /sbin/mount.ntfs-3g as described in debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560780 2. Default file permissions are hardlinked in devicekit so that source files must be changed to the more appropriate ones as desciribed in ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/devicekit-disks/+bug/482501
as the hal->devicekit->udisk->whatever transition is all but unclear in many aspects yet I'm not sure when this'll get fixed.
As explained by David Zeuthen in https://bugs.freedesktop.org/show_bug.cgi?id=27046 "Actually the way this is supposed to work is that mount options (if the default mount options are not good enough) are supposed to be originating from the automounter (typically running in the desktop session). It worked this way with HAL and it also works this way with udisks. It is true that gnome-mount used to read these settings from gconf and pass it to HAL's Mount() method. This however changed when GVfs entered the picture and Nautilus started automounting instead of gnome-volume-manager. Btw, GVfs will not read mount settings from anywhere since we believe that the defaults are good enough for common uses and the user can always override using /etc/fstab. For more information about why we think this is so in GNOME, see https://bugzilla.gnome.org/show_bug.cgi?id=586708" Then, this should be done in gvfs and, probably, this bug could be closed as it is an enhancement request that should be covered by upstream
Closing upstream per last comment. There is nothing for us to do. Fixing this implies reporting a bug to upstream, either nautilus of gnome-disk-utility maybe.
>1. If ntfs-3g will be used as a default, then there should exists >/sbin/mount.ntfs symlinked to /sbin/mount.ntfs-3g as described in debian bug: >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560780 Seems like a hack. I guess the proper way would be having the below .fdi converted to a udev rule. For the devicekit-disks/udisks/udev/gudev, or whatever it's called today, case. http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-fs/ntfs3g/files/10-ntfs3g.fdi.2009-r1?rev=1.1&view=markup
*** Bug 310447 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > >1. If ntfs-3g will be used as a default, then there should exists > >/sbin/mount.ntfs symlinked to /sbin/mount.ntfs-3g as described in debian bug: > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560780 > > Seems like a hack. I guess the proper way would be having the below .fdi > converted to a udev rule. For the devicekit-disks/udisks/udev/gudev, or > whatever it's called today, case. > > http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-fs/ntfs3g/files/10-ntfs3g.fdi.2009-r1?rev=1.1&view=markup > That does not work, only way to do it was that hack :( I tried several udev rules but none seemed to work. If you try and verify I will be very happy (my udisks/devicekit-disks does not understand or obey the rule)
Creating /etc/udev/rules.d/99-ntfs3g.rules with the following works for me ENV{ID_FS_TYPE}=="ntfs", ENV{ID_FS_TYPE}="ntfs-3g" I suppose this could be included with the ntfs3g package like with the hal .fdi file. Still, not the most elegant solution, changing the reported file system type.
I tested #9, it works and I think we should fix it.
then this issue should be reassigned to ntfs3g maintainer. It would probably be best to have it under a udev USE flag in order to not mess with users that actually want another default ntfs mounter.
+1 (Reassigning to ntfs3g maintainer for consideration -> please read comment #9 )
Added udev USE flag to sys-fs/udev-2010.3.6 to install workaround udev rule from comment #9.
Thanks Patrick for the fast fix :-)
it solve the problem with external disk but if you have some local ntfs disk it dont automout it with USE="suid", maybe dev can fix this or add a udev rules for automount of local ntfs or fat16/32 patition by default too. thanks
I am not sure what you are trying to describe there, but if there is another issue with ntfs3g, please open another bug.
*** Bug 328169 has been marked as a duplicate of this bug. ***
