Setting an invalid mount point can make a removeable media unaccessible
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-mount |
Expired
|
Critical
|
|||
gnome-volume-manager |
Invalid
|
Undecided
|
Unassigned | ||
gnome-mount (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Jaunty |
Fix Released
|
High
|
Martin Pitt | ||
gnome-volume-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-volume-
When accessing the properties of a mounted media and changing the mount point option on the "Volume"-Tab, one can set a mount point to use for that volume. It seems that this only referes to the last part of the "real" mount point, so one is expected to enter "foo" when the volume should be mounted on "/media/foo". This might be better for novice user, but I tried entering "/media/foo", which was accepted without a problem. Unfortunately when re-plugging the device back in it a warning dialog pops up that says "Cannot mount volume. Unable to mount volume" . When clicking details the message "mount_point cannot contain the following characters: newline, G_DIR_SEPERATOR (usually /)".
Only changing the key /system/
I suggest two changes:
* The properties dialog should check for valid values and not allow a "/" to be entered
* The volume should be mounted in its default location, if the user specified location is not valid.
Related branches
Changed in gnome-volume-manager: | |
status: | Unknown → New |
Changed in gnome-mount: | |
status: | Unknown → New |
Changed in gnome-mount: | |
status: | New → Confirmed |
Changed in gnome-mount: | |
importance: | Unknown → Critical |
status: | Confirmed → Expired |
Thank you for your report. I can confirm this at an up-to-date feisty amd64.
I think the first point you mentioned is a bug(if you aren't familiar computers, you wouldn't be able to solve it)
The second point is more a wish list, although it is a sort of backup safety.