does not honor /system/storage/volumes mount point override

Bug #423058 reported by Per Ångström
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
devicekit-disks (Ubuntu)
Won't Fix
Wishlist
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Migrating from Jaunty to Karmic (Alpha 4) I notice that nautilus does no longer honor the mount points I have manually chosen for my removable devices.

I have the following key, which worked in Jaunty:
/system/storage/volumes/_org_freedesktop_Hal_devices_volume_uuid_F0EA4C40EA4C04F6: mount_point=Passport

However, Karmic nautilus mounts the drive on "media/WD Passport". I also notice that the GUI for changing mount points has disappeared from the Properties dialog.

I think this has to do with the move from HAL to DeviceKit.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
summary: - [karmic regression] nautilus does not honor /system/storage/volumes
- mount point override
+ does not honor /system/storage/volumes mount point override
Revision history for this message
Sebastien Bacher (seb128) wrote :

the key was probably a gnome-mount thing, not sure if nautilus or devicekit-disks should be doing that now

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This currently isn't supported by devicekit-disks (and might not ever be). Specifying mount paths is really only useful for internal disks, for which /etc/fstab is more flexible anyway. You can also easily change volume labels now, which the mount points are based upon anyway.

affects: nautilus (Ubuntu) → devicekit-disks (Ubuntu)
Changed in devicekit-disks (Ubuntu):
importance: Low → Wishlist
Revision history for this message
Martin Pitt (pitti) wrote :

Right, this was discussed with upstream, and they don't plan to put it back. Given that it's now easy to change the labels of disks with System -> Admin -> Disk Utility, there is no really high need for this any more.

Changed in devicekit-disks (Ubuntu):
status: New → Won't Fix
Revision history for this message
Per Ångström (autark) wrote :

OK, so I tried to change the label of an NTFS-formatted volume in Disk Utility:

Error changing fslabel: helper exited with exit code 1: fstype ntfs not supported

Revision history for this message
maxstirner (philipp-d) wrote :

"Given that it's now easy to change the labels of disks with System -> Admin -> Disk Utility, there is no really high need for this any more."

This doesnt work with encrypted disks..

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 423058] Re: does not honor /system/storage/volumes mount point override

maxstirner [2009-10-10 11:10 -0000]:
> This doesnt work with encrypted disks..

There is no reason why it shouldn't. Please file this as a separate
bug with detailled reproduction steps if you actually have that
problem (works fine for me).

Revision history for this message
nieproszenieja (mateusz-szulc) wrote :

Although setting label in Disk Utility works for me (and now I think that is probably better than /system/storage/volumes entries), I spend 3h searching, why Karmic doesn't mount usb harddisk in mount point specified through gnome-mount.

I used command:
gnome-mount --write-settings -d /dev/sdX --mount-point sdX

and there was no warning, that this options won't work anymore. Furthermore, 'gnome-mount --display-settings' reported, that mount point is now this one, which I specified. So why this option (--write-settings) still exist, while it doesn't work anymore in Karmic's GNOME? And why the entries in gconf (/system/storage/volumes) still exist?

I think its very a stupid habit to remove some functionalities without warning about the user. This shouldn't be done in that way.

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

Other bug subscribers

Remote bug watches

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