Nautilus 2.22.5.1 (x64) cannot mount optical drives [SOLVED]

[tomblue]

Hi all,

when I click on the CD/DVD icon in Nautilus I'm getting a message "Unable to mount location. Can't mount file".

I'm a bit clueless as mounting a CD/DVD from commandline (mount /dev/cdrom) works perfectly. Automatic mount of a USB-stick within Gnome/Nautilus works as well. As the same behaviour can be observed when logged in as root, I suspect that this is not some kind of permission glitch.

Is there a way to get more information out of Gnome/Nautilus to get more detailed information why the mount fails? Am I missing a package [I've installed ~amd64 gnome-base/gnome-light-2.22.0]. Did someone solve a similar problem?

Thanks a lot.

[OldTango]

Hi all,

when I click on the CD/DVD icon in Nautilus I'm getting a message "Unable to mount location. Can't mount file".

I don't have an answer to this problem, but I have suffer from the same issue ever since gnome was updated.

Auto-mounting works fine for my usb devices and optical drives and media. However auto-mounting any internal optical drive fails completely. I am still searching through all the bug reports for clues to this issue. I don't know if the issue happens on x86 installs or not as I haven't upgraded my x86 systems yet and I won't until I can find a solution to this issue on amd64.

Anyone have any ideas on how to solve this problem............

TIA..............

[uxbod]

Looks like I am having the same problem - thought it was just me Still working the issue.

[OldTango]

Some of it has to do with having entries in /etc/fstab for the optical drives as well as any floppy drive. If I comment out the entries nautilus will mount media placed in the drives. This allows most media to sometimes mount and be used by a selected application, but is real clunky with unpredictable results. However it is buggy at best as it mounted a data disc the first time I inserted it, but on additional tries in the same drive it failed complaining about some mount point problem. If I put the same data disc into my other optical drive it mount just fine.

At this point in time one of my optical drives will mount any disc inserted but the other only mounts data disc's so far...............


I am fairly sure commenting out the relevant sections in fstab will make manually mounting the drives and media in them a problem on the command line, even though I haven't tested for this condition yet.

[Nick C]

post your /etc/fstab, theres probably a simple fix to it

[OldTango]

Here is my fstab. As you can see I have commented out the entries for the optical drives and the floppy so nautilus can mount media inserted into these drives. I have used this setup in my fstab for several years now without problems. The Upgrade to Gnome-2.22 is when things went wrong. I waited to upgrade till Gnome-2.22 went stable and I followed the upgrade guide.

Code: Select all

# <fs>			<mountpoint>	<type>		<opts>		<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sda1		/boot		ext2		noauto,noatime	1 2
/dev/sda3		/		ext3		noatime		0 1
/dev/sda2		none		swap		sw		0 0
#/dev/hda		/mnt/cdrom	auto		noauto,ro,user	0 0
#/dev/hdb		/mnt/cdrw	auto		noauto,rw,user	0 0
#/dev/fd0		/mnt/floppy	auto		noauto,user	0 0

# NOTE: The next line is critical for boot!
none			/proc		proc		defaults	0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for 
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
none			/dev/shm	tmpfs		nodev,nosuid,noexec	0 0

If I don't comment out those lines nautilus refuses to see or mount any media inserted in any of these drives. I get the error "Unable to mount location. Can't mount file" or "there is no media in the drive."

The gnome-2.22 upgrade guide says this

Automounting has seen a few significant changes for Gnome 2.22. It is now handled by Nautilus instead of gnome-base/gnome-volume-manager. However, gnome-volume-manager is still used to detect new hardware such as cameras.

Because of this change, there is now an automount use flag on gnome-volume-manager for users who wish to keep the old behavior. Users who previously started gnome-volume-manager with non-Gnome desktops are strongly advised to enable this use flag. Gnome users on the other hand are strongly advised to make sure that this use flag is not turned on, as it will cause problems with Nautilus.

Its seems that this is a new feature in gnome and it isn't working so well at the moment.

TIA

[tallica]

Same here. I had to comment line in fstab to get optical driver automount. Same with/without automount flag for gnome-volume-manager.

Code: Select all

#/dev/sr0	/mnt/dvd		auto		noauto,user						0 0

[tomblue]

Same here. I had to comment line in fstab to get optical driver automount. Same with/without automount flag for gnome-volume-manager.

Code: Select all

#/dev/sr0	/mnt/dvd		auto		noauto,user						0 0

Yep, commenting the optical drive entry in "/etc/fstab" did the trick for me as well!

Thanks a lot for your help!

[dopey]

The problem with commenting out the drive entries in /etc/fstab is that by default nautilus/hal seems to want to mount the drive as /media/[VOL LABEL]. This is obnoxious for applications like crossover and other things that like to refer to the CD devices by a static directory for their mount points.

Anyone figure out how to get nautilus to actually work with a fixed directory name that optical drives mount to?