ntfs-3g support?
Bug #75791 reported by
Mikael Nilsson
This bug report is a duplicate of:
Bug #78375: [patch] ntfs-fuse and ntfs-3g support for gnome-mount.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-mount (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi!
I'm using an updated feisty, with gnome-mount 0.5-2ubuntu3. I have givré's ntfs-3g packages installed (http://
Now, in edgy, plugging in an external device worked fine, and using pmount manually also works fine. But letting it mount automatically gives it the wrong charset (should use UTF-8), so files with non-ascii characters won't show.
I was under the impression that gnome-mount would support ntfs-3g, so you might want to know about the issue.
I'd be happy to help debug this if necessary.
To post a comment you must log in.
Hi,
gnome-mount actually replace pmount, and so it use a different method.
Basically, gnome-mount support ntfs-3g, as soon as you tell hal to use ntfs-3g for all ntfs device. This can be done by an .fdi file.
If you install my modified pmount package (even if you don't need pmount anymore), you get this kind of file, and it's probably why it works automatically.
The problem is that, ntfs-3g use a different local option than the kernel driver.
- With the kernel driver, a simple "utf8" is enough, and this is what do gnome-mount
- ntfs-3g use a "local=××_××.××" option (ex : en_US.utf8, fr_FR.utf8), and so this option may change with your configuration.
pmount set the local in the program, so you can get the local by calling setlocale( LC_ALL, "" ) and setting it for ntfs-3g. But as far as i know, gnome-mount use a config file, so setting automatically the local option is a bit tricky.
Any idea martin ? I don't run yet feisty, so i can't really investigate the problem.