Nautilus crashes when opening mass storage (Garmin etrex 20 GPS)

[Willem Ferguson]

I use a Garmin Etrex 20 GPS that can function as a mass storage device.
When I open the mass storage device, Nautilus hangs the whole Ubuntu UI.
When I use a Virtualbox VM of Fedora 22 on the same Ubuntu host, Fedora
opens the mass storage device perfectly.
Does this mean there is a problem with USB access of mass storage
devices on Ubuntu 15.04?

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu9.1
ProcVersionSignature: Ubuntu 3.19.0-39.44-generic 3.19.8-ckt9
Uname: Linux 3.19.0-39-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Dec 20 21:40:20 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'smaller'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']"
InstallationDate: Installed on 2015-07-28 (145 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_ZA.UTF-8
 LANGUAGE=en_ZA:en
 XDG_RUNTIME_DIR=<set>
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.