Disks manager doesn't set right permissions when mounting

Hmmm no reactions yet. I think it is pretty important this is fixed before
breezy is released, otherwise half the functionality of the disk manager is
gone... (or is it only me experiencing this?)

Thanks for your bug. That works fine for me. What version of the package do you
use? How do you create the folder?

Running 1.4.0-0ubuntu4.

Found out a little bit more:

When creating a directory by clicking on a disk -> partitions -> choose a
partition -> access path:change -> create folder The permissions are set like this:
drwxr-xr--
so I can't access it

When I then mount an ext3 partition to it, all is fine:
drwxr-xr-x

But when mounting a NTFS partition to it:
dr-x------
Which makes it completely useless...

> When I try to mount my windows partition with disks manager,
> I cannot access it other than with browse from the disks
> manager window.

same for me (Colony 5)

the cause of the problem is the missing option umask=0 in mount (per default,
NTFS partition can only be read by root)

generally, the disks-admin would be much more useful, if the mount/unmount
information would be saved in /etc/fstab

currently, after rebooting all settings done with disks-admin are lost

finally, the program lacks german translations (couldn't find disks-admin in
rosetta) and help (remove the help button if no help is available)

further explanation: accessing the Windows partition actually works when it is
done using the 'Browse' button of the disk-manager; the reason: disk-manager
runs with root rights and starts nautilus, also with root rights; bingo!

however, if you open a new instance of Nautilus using the Gnome menu Locations
(i.e. starting Nautilus with normal user rights), it is impossible to open the
directory where the windows partition is mounted

------

another problem with disk-manager: it should use the mount option utf8 for NTFS
partitions; without it, all file names which use non-ASCII characters are
displayed wrong (Nautilus says 'invalid encoding')

I have not tested this for FAT partitions (none available here), so I don't know
if the same problem is there as well; just in case: the right mount option for
FAT would be iocharset=utf8

iocharset=utf8 on vfat will give you a warning that it makes the filesystem case
sensitive, which Windows obviously doesn't like. Bad idea. I think utf8=true is
the safe way of doing it, I'll confirm when I get back to my linux machine later
today.

(In reply to comment #5)
> disk-manager
> runs with root rights and starts nautilus, also with root rights; bingo!
>
That is http://bugzilla.ubuntu.com/show_bug.cgi?id=17049

/dev/hda1 /mnt/windows ntfs user,nls=utf8,umask=0222 0 0
/dev/hdb1 /storage/windows2 vfat user,utf8=true,umask=000
0 0

are the settings for my NTFS and FAT32 drives, that let regular users access
them with correct codepages.

I filed Bug #36665 about the issue of NTFS partitions being set up with no access at install time. You may be interested.

That's a duplicate of bug #25071 which is fixed now

The duplicate of this bug is marked as fixed, so this should be fixed now. please reopen the bug if you still see the problem.