Users need guidance for: "Cannot mount volume." message

Bug #236309 reported by Duncan Lithgow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-mount
Expired
Low
gnome-mount (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

I am the admin of my pc.

_After_ installing hardy I added a SATA HD with several partitions. I assume that is why those volumes are not automounted. Normally I would add them via fstab, but the permissions system in 8.04 showed me some option under 'Properties > Volume' which I thought would take care of this for me. So I added some settings which turned out to be a problem (volume is vfat):

Cannot mount volume.
Unable to mount the volume 'STORAGE1'.
Details
mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /)
[ OK ]

... my bug is that this message/ popup does not help me solve the problem because it gives no indication of where to adjust the settings. There is no new entry in /etc/fstab so it's not there.

I assume that a 'Help' button linked to the relevant section of the documentation would close this bug, or at least make it a documentation bug - which is easier to fix.

(Solving the cause of this error message is a question here: https://answers.edge.launchpad.net/ubuntu/+source/nautilus/+question/34812)

Tags: hardy vfat
description: updated
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, could you describe how to trigger the bug on a stock installation? it seems to be specific to your configuration, maybe you could open the bug on bugzilla.gnome.org since you can reply to their comments, having somebody not getting the bug sending comments between bugs trackers would not be efficient

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote : Re: [Bug 236309] Re: Users need guidance for: "Cannot mount volume." message

@Sebastian
This is a vanilla install, until I tried to use the settings in
'Properties > Volume'.

I'm happy to report this in gnome, but against what part of nautilus?
(I find their system pretty cluttered with bits I don't understand.)

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

select a component, you can use GIO which is the new nautilus gvfs version

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

gnome-mount do the mounting, reassigning the bug

Changed in nautilus:
status: Incomplete → New
Changed in gnome-mount:
status: Unknown → New
Changed in gnome-mount:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

comments from upstream:

"Which settings did you tweak/set under "Properties"->"Volume"?
I haven't fully understood if your bug is about not being able to mount the
volume or about the error message.
"

Changed in gnome-mount:
status: New → Incomplete
Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

I have replied upstream.

Changed in gnome-mount:
status: Incomplete → New
Changed in gnome-mount:
status: Incomplete → Triaged
Changed in gnome-mount:
status: New → Incomplete
Changed in gnome-mount:
importance: Unknown → Low
Changed in gnome-mount:
status: Incomplete → Expired
Revision history for this message
Phillip Susi (psusi) wrote :

This package has been removed from Ubuntu. Closing all related bugs.

Changed in gnome-mount (Ubuntu):
status: Triaged → Invalid
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.