mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /)

Bug #88828 reported by Lorenzo Ferrara
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-mount (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: gnome-mount

Hello,
I have a Samsung YP-U1 1 GB OGG/MP3 Player and I use Feisty.
I never had problems with the digital audio player and Feisty.
Now I just did an apt-get update, apt-get dist-upgrade and this is what I have:

when I insert the player in the usb slot gnome-mount gives:
-------------------------------------------------------------------------------
Cannot mount volume.
Unable to mount the volume 'samsung1gb'.
Details
mount_point cannot contain the following characters:
newline, G_DIR_SEPARATOR (usually /)
-------------------------------------------------------------------------------

than nautilus comes up and te volume gets mounted ok.
dmesg gives:
-------------------------------------------------------------------------------
[ 5331.311000] usb 4-4: new high speed USB device using ehci_hcd and address 10
[ 5331.426000] usb 4-4: configuration #1 chosen from 1 choice
[ 5331.428000] scsi5 : SCSI emulation for USB Mass Storage devices
[ 5331.428000] usb-storage: device found at 10
[ 5331.428000] usb-storage: waiting for device to settle before scanning
[ 5336.428000] usb-storage: device scan complete
[ 5336.428000] scsi 5:0:0:0: Direct-Access Samsung YP-U1 0100 PQ: 0 ANSI: 4
[ 5336.431000] SCSI device sda: 511552 2048-byte hdwr sectors (1048 MB)
[ 5336.431000] sda: Write Protect is off
[ 5336.432000] sda: Mode Sense: 3e 00 00 00
[ 5336.432000] sda: assuming drive cache: write through
[ 5336.436000] SCSI device sda: 511552 2048-byte hdwr sectors (1048 MB)
[ 5336.437000] sda: Write Protect is off
[ 5336.437000] sda: Mode Sense: 3e 00 00 00
[ 5336.437000] sda: assuming drive cache: write through
[ 5336.437000] sda: sda1
[ 5336.439000] sd 5:0:0:0: Attached scsi removable disk sda
[ 5336.439000] sd 5:0:0:0: Attached scsi generic sg0 type 0
[ 5342.085000] UDF-fs: No partition found (1)
[ 5342.227000] Unable to identify CD-ROM format.
-------------------------------------------------------------------------------

This is how I formatted the partition on the player.
-------------------------------------------------------------------------------
root@port0:/# mkfs.vfat -F 16 -S 2048 -n samsung1gb /dev/sda1
mkfs.vfat 2.11 (12 Mar 2005)
root@port0:/#
-------------------------------------------------------------------------------

Versions:
-------------------------------------------------------------------------------
    gnome-mount > 0.5.2ubuntu4
            hal > 0.5.8.1-4ubuntu8
libhal-storage1 > 0.5.8.1-4ubuntu8
      mkfs.vfat > 2.11 (12 Mar 2005)
       uname -a > Linux port0 2.6.20-9-lowlatency #2 SMP PREEMPT Mon Feb 26 03:04:39 UTC 2007 i686 GNU/Linux
-------------------------------------------------------------------------------

description: updated
description: updated
description: updated
Revision history for this message
Lorenzo Ferrara (lorenzoferrara) wrote :

More on the topic:

If I unmount the volume using gnome then gnome-umount gives me:
---------------------------------------------
Cannot unmount volume
The volume 'samsung1gb' was probably mounted manually on the command line.
Details
Device to unmount is not in /media/.hat-mtab so it is not mounted by HAL
---------------------------------------------

And the volume is not unmounted.
dmesg doest not give any info.

When I insert the digital player in the usb slot I get the error shown in the firt post and the volume gest mounted but not in
/media/samsung1gb/

but in
/media/sda1/

description: updated
Revision history for this message
Lorenzo Ferrara (lorenzoferrara) wrote :

I don't think this bug affects gnome-mount, but I can't tell the package that is involved.

Revision history for this message
Martin Pitt (pitti) wrote :

Can you please do

  lshal > hal.txt

(with the player plugged in) and attach hal.txt here?

Changed in gnome-mount:
status: Unconfirmed → Needs Info
Revision history for this message
Lorenzo Ferrara (lorenzoferrara) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

If you are on feisty, you should not have a /media/.hal-mtab directly after booting, can you confirm? Then, please do the following:

  - boot and log in without the stick attached
  - killall gnome-volume-manager
  - gnome-mount -vbd /dev/sda1

what does the last command print out? Please copy&paste it here

Revision history for this message
Lorenzo Ferrara (lorenzoferrara) wrote :

here is the copy & paste
--------------------------------------------------------------
user@port0:~$ gnome-mount -vbd /dev/sda1
gnome-mount 0.5
libhal-storage.c 1401 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set.
** (gnome-mount:5697): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_45E6_221C
** (gnome-mount:5697): DEBUG: read mount point '/media/samsung_1gb' from gconf string key '/system/storage/drives/_org_freedesktop_Hal_devices_storage_serial_Samsung_YP_U1_0002F9AFB0884505/mount_point'
** (gnome-mount:5697): DEBUG: read default option 'shortname=mixed' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:5697): DEBUG: read default option 'uid=' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:5697): DEBUG: read default option 'utf8' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:5697): DEBUG: read default option 'umask=077' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:5697): DEBUG: read default option 'exec' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:5697): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_45E6_221C with mount_point='/media/samsung_1gb', fstype='', num_options=5
** (gnome-mount:5697): DEBUG: option='shortname=mixed'
** (gnome-mount:5697): DEBUG: option='uid=1000'
** (gnome-mount:5697): DEBUG: option='utf8'
** (gnome-mount:5697): DEBUG: option='umask=077'
** (gnome-mount:5697): DEBUG: option='exec'

** (gnome-mount:5697): WARNING **: Mount failed for /org/freedesktop/Hal/devices/volume_uuid_45E6_221C
org.freedesktop.Hal.Device.Volume.UnknownFailure : mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /)
--------------------------------------------------------------

Revision history for this message
Nicolas Bourdais (nbourdais) wrote :

I get this message when I try to change the mount point through 'Properties'-->'Volume'-->'Mount point'.
But it can be different as my stick isn't mounted at all and nautilus doesn't come up.

However, forcing the mount point creates a key in gconf which I have to delete to mount again my stick.
/system/storage/volumes/_org_freedesktop_Hal_devices_volume_uuid_4620_CAE4/mount_point

And it seems you've got such a key (mine is under 'volumes' and yours is under 'drives') :

** (gnome-mount:5697): DEBUG: read mount point '/media/samsung_1gb' from gconf string key '/system/storage/drives/_org_freedesktop_Hal_devices_storage_serial_Samsung_YP_U1_0002F9AFB0884505/mount_point'

Try to delete this key whith gconf_editor. I think you won't get any message, but your stick will not be mounted at /media/samsung1gb/

I consider this as a bug. Or tell me what kind of mount points I can choose without entering '/' ?

Nicolas Bourdaos

Revision history for this message
Nicolas Bourdais (nbourdais) wrote :

I think i'm dumb.

Just change this key :
system/storage/drives/_org_freedesktop_Hal_devices_storage_serial_Samsung_YP_U1_0002F9AFB0884505/mount_point

from '/media/samsung_1gb' to 'samsung_1gb'

It will just work.

But it's a bit troubling when you change the mount point through the properties to see :
"Mount point : /media/cle"
Parameters-->"Mount point : cle"

Here is a capture of my stick's properties for you to see (mount point is 'point de montage in french').

Perhaps nautilus properties could be changed from 'mount point' to name or label for the parameters part.

Nicolas Bourdais

Revision history for this message
Lorenzo Ferrara (lorenzoferrara) wrote :

Just upgraded to feisty and all work well. I didn't change any configuration. Just works.

Thanks

Lorenzo Ferrara

Revision history for this message
Lorenzo Ferrara (lorenzoferrara) wrote :

Sorry,
problem is still here.

But changing this

system/storage/drives/_org_freedesktop_Hal_devices_storage_serial_Samsung_YP_U1_0002F9AFB0884505/mount_point

from '/media/samsung_1gb' to 'samsung_1gb' resolves it.

Thanks to all!!

Lorenzo Ferrara

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-mount (Ubuntu) because there has been no activity for 60 days.]

Revision history for this message
Marcus Dapp (digisus) wrote :

Hi,

I just ran into the same problem (using Gutsy) and I know what the problem is. A user can change the mount point in the context-menu of a mounted disk by entering a different mount point, see screenshot. The problem is that the user is led into a trap as it seems one has to enter a full mount path beginning with "/media/.." but in actuality what the user has to enter is -only- the directory name where the device should be mounted to.

In the screenshot: To get the USB stick mounted to /media/fatty, I only have to enter "fatty" and -not- the whole path. BUT the GUI misleads me because the old mount point is given a full path.

Solution: Change the GUI to make clear that the user only has to enter the directory name and not the full path.

Martin Pitt (pitti)
Changed in gnome-mount:
status: Invalid → Confirmed
Revision history for this message
benamsee (benamsee) wrote :

Had the same problem.
Marcus Dapp's solution worked quite fine with my device.

Thanks.

Revision history for this message
Ryan Sinn (ryan-sinn) wrote :

I've had the same issue now -- how can an older bug be the duplicate of a newer bug?

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.