Public bug reported:

This is yet another report of USB storage devices failing to automatically 
mount on some hardy and
intrepid desktops. This appears to be confined to machines that have been 
upgraded from a previous release. 

Things this problem is NOT:

* A kernel issue. dmesg reports the drives and partitions to be found. Removing 
USB 2.0 support (ehci_hcd) makes no difference.
*  A USB flash specific problem. My external hard drive with both vfat and ext3 
partitions will not automount, either.
* A udev issue. Device entries are created in the usual places, matching those 
found on a working hardy installation.
* A HAL issue. lshal reports the same new entries on both a working hardy 
install, and the problematic hardy and intrepid installs.
*  A Dbus issue. qdbusviewer (from the qt4-dev-tools package) shows items 
appearing on the system bus used by HAL.
*  A gnome-mount issue. gnome-mount with a device argument completes the mount 
as expected, with an icon appearing on the desktop, and nautilus opening a 
browser window if configured to do so.
* A installer related symptom. There is no entry for any of the device names 
that udev creates in fstab or blkid.tab which can conflict (by considering the 
device to be a cdrom, for example), which is occasionally a problem created by 
the installer, particularly on USB device installs.

I can confirm that Nautilus is set to mount new hardware and open
browser windows.

I can confirm that the problem persists if I log in as a newly created
user, which suggests that this is not a problem with a legacy setting
left in the user's gconf or other settings.

Both the new user, and the user created within the older installation
are members of plugdev, fuse, cdrom and floppy amongst others.

The major difference between the machine that does work, and the ones
that don't is that the working machine has a copy of gnome-volume-
manager running. If I run gnome-volume-manager on the broken machines,
with the -n switch, they exit with the "live and let die" message, which
apparently means that some other program (Nautilus, perhaps) is
listening to Dbus and handling mounting (according to
http://www.mattcutts.com/blog/intrepid-ibex-failing/).

Unfortunately, this is as far as I can get.
https://wiki.ubuntu.com/DebuggingRemovableDevices desparately needs to
be updated to include an overview of the auto mounting process for each
of the Ubuntu releases, and we need some way of prying debugging
information out of which ever process is responsible for handling
automounting now.

** Affects: nautilus (Ubuntu)
     Importance: Undecided
         Status: New

-- 
USB storage do not automatically mount
https://bugs.launchpad.net/bugs/302679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to