Does not automount hotplugged WALKMAN NWZ-E438F device

[Maxim Dobriakov]

Binary package hint: gvfs

Auto-mount for WALKMAN NWZ-E438F in Ubuntu 9.10 work fine. After I have made upgrade to Ubuntu 10.04 Beta 2 and auto-mount stopped work.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gvfs 1.6.0+git20100414-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sat Apr 17 20:40:46 2010
HotplugNewDevices: /dev/sdb /dev/sdb1
HotplugNewMounts:

ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gvfs
Symptom: storage
Title: Does not detect hotplugged storage device

[Sebastien Bacher (seb128)]

Thank you for your bug report, the logs seem to indicate the device is detected and a gvfs mount is added too, do you get the icon added in the computer location?

[Maxim Dobriakov (closer-main)]

I don't see icon related to Walkman storage on my desktop (or in "Places" menu).

FYI: I can mount Walkman storage use System => Administration => Disk Util tool. After that I see Walkman storage icon on my desktop and have access to files on device.

[Martin Pitt (pitti)]

gvfs output looks good indeed. After plugging in the walkman, please copy&paste the output of

  mount
  gvfs-mount -d /dev/sdb1
  mount

Thanks!

[Maxim Dobriakov (closer-main)]

I have attached log. First part of log contains "mount" output without device. Second part contains output for commands described above. After these commands I see Walkman icon on desktop and has access to files on it.

[Martin Pitt (pitti)]

Hm, so gvfs correctly detects the device, and gvfs-mount works, too. So this rather sounds like an issue in nautilus then (which does the automounting).

Can you please copy&paste the output of

  ps ux|grep nautilus
  gconftool -R /apps/nautilus/preferences|grep media

? Thanks!

[Maxim Dobriakov (closer-main)]

Output for commands described above:

closer@coreduo:~$ ps ux | grep nautilus
closer 1705 0.3 0.9 106756 19644 ? Sl 22:15 0:00 nautilus
closer 2146 0.0 0.0 3324 812 pts/0 S+ 22:18 0:00 grep nautilus
closer@coreduo:~$ gconftool -R /apps/nautilus/preferences|grep media
 media_autorun_x_content_start_app = [x-content/audio-player]
 media_automount_open = true
 media_autorun_x_content_ignore = [x-content/software]
 media_autorun_never = false
 media_automount = true
 media_autorun_x_content_open_folder = [x-content/audio-player]
closer@coreduo:~$

Question: How about GLib-GIO-CRITICAL assertion messages which caused gvfs-mount? Is it normal behavior?

[Maxim Dobriakov (closer-main)]

Yes! I have found problem! As you can see above the property media_autorun_x_content_ignore set to [x-content/software]. Using nautilus preference dialog I have changed this property (for combobox "Software" selected "Open Folder" value). But this is didn't resolve problem. On the next day I restart computer and connect player and auto-mount open folder on device.

Now I have two questions:
1) Is it possible what upgrade script changed this property?
2) I have made restart for applying nautilus settings. I thing this is not clear behavior. Right?

[Martin Pitt (pitti)]

Ah, I have

 media_autorun_x_content_start_app = [x-content/software]
 media_autorun_x_content_ignore = []

Which is the default.

These are usually set in your ~/.gconf/ files, which aren't (and can't even) be touched on upgrades. Also, I haven't seen this problem in other reports, so for now I have to assume that this is a local configuration problem only.

Do you have some third-party software installed which might have done this? Perhaps you can try this in the guest session or a freshly created user?

[Launchpad Janitor (janitor)]

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