gvfs mounts with 0700 permissions

Bug #390040 reported by Taylor "Ripps" LeMasurier-Wren on 2009-06-20
This bug affects 18 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)

Bug Description

Binary package hint: devicekit-disks

In Ubuntu Karmic Alpha2, devkit-disk mounts the disk as 0700, which prevents programs like mpd from being able to read the disk. devkit should mount the disks as read/write for the user and read for everybody else.

Martin Pitt (pitti) wrote :

devkit itself defaults to 0700, but does allow clients to specify other mount options (devkit-disks --mount-options "dmask=022" --mount /dev/sdb1). Also, Ubuntu defaulted to mounting external disks with user-only privileges to protect private data.

However, earlier Ubuntu versions allowed you to set individual mount options through the GUI. This functionality isn't currently exposed in nautilus any more.

summary: - Devkit-disk breaks mpd symlinks to external harddisk
+ Devkit-disk mounts with 0700 permissions
summary: - Devkit-disk mounts with 0700 permissions
+ gvfs mounts with 0700 permissions
affects: devicekit-disks (Ubuntu) → nautilus (Ubuntu)
Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Martin Pitt (pitti) wrote :

I remember having discussed this with David recently, and they don't plan to bring back the fine-grained mount options to GNOME; unfortunately I just can't find it right now. Much rather this should become an option like "share this device with all users" somewhere.

Sebastien Bacher (seb128) wrote :

There is a similar discussion on http://bugzilla.gnome.org/show_bug.cgi?id=586708

glorybox (glorybox-away) wrote :

Any progress on this bug?

Is there a way to specify different mount options to devkit?

Fabio Marzocca (thesaltydog) wrote :

Why this bug is marked as "Low"?

Leo (leorolla) wrote :

It is hard-coded. That's bad.

Stripping whatever is hard-coded and reading it to a text file would be great.

How did Nautilus decide the mount options for a FAT or NTFS hot-plugged disk? Where is it written? If it's still some .c file then it should definitely be fixed.

I myself really do hate all the rsync/unison problems I get every time summer comes or every time I change countries, so I would for instance add tz=UTC as a mount option for FAT32 to my configuration file. But if it is really that important that the users who created their files at 6:13 in their dual-boot operating system see it as 6:13 in Ubuntu, then maybe it's better not to have tz=UTC as default, and let rsync users do their manual change. But having to patch .c filees, apt-get build-dep etc etc etc etc, that is ugly.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.