When you enter a typo in Drive or Volume tabs of Properties dialog, the volume will not mount anymore and you can't correct the mistake

Bug #382114 reported by Ricardo Pérez López
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-mount (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: gnome-mount

Steps to reproduce:

1. Go to Places->Computer.
2. Right-click on any volume and select Properties (the volume must be previously mounted).
3. Click on Drive or Volume tabs.
4. Click on Settings to show the mount options.
5. Enter any wrong information in the "Mount point", "Filesystem" or "Mount options" fields. Try, for instance, entering "foo" (without the quotes) in "Mount options" field and enter "good" or reasonable values in the other two fields.
6. Unmount the volume and try to mount it again.

Result: An error dialog appears indicating that the volume couldn't be mounted (as expected, because you entered wrong mounting options on step #5). However, you can't fix the wrong options because you can't access to the Drive and Volume tabs until the volume has been mounted, and you can't mount the volume because the mount options are wrong. There's no way to fix the bad options entered on step #5.

The bug is fully reproducible and could lead to have an inaccessible volume without an easy way to repair the access to the volume.

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

What version of Ubuntu are you using? This sounds like bug 107668 which is already fixed in Jaunty. Or it could also be bug 231218

Changed in gnome-mount (Ubuntu):
status: New → Incomplete
Revision history for this message
Ricardo Pérez López (ricardo) wrote :

Thanks for the reply. I'm using Ubuntu 9.04, fully updated. Now I can see that it seems to be the same issue as bug #231218, as you said.

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.