Unable to unmount Nexus 4: The connection is closed

Bug #1253187 reported by Andreas Jonsson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs
Invalid
Medium
gvfs (Ubuntu)
Fix Released
Low
Philip Langdale

Bug Description

When I click the "eject" triangle next to my Nexus 4 in Nautilus this error message appears (see title/screenshot). I am uncertain whether the phone actually unmounts or not so that it is safe to disconnect it.

After the error message appears I can still access the phone content at /run/user/1000/gvfs/mtp..., which suggests that the phone is still mounted.

"sudo umount /run/user/1000/gvfs" properly unmounts the phone.

Expected behaviour: To receive a confirmation message from Nautilus saying it is now safe to disconnect the phone.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Wed Nov 20 13:25:42 2013
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'685x847+753+24'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'174'
InstallationDate: Installed on 2010-04-30 (1300 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MarkForUpload: True
SourcePackage: nautilus
UpgradeStatus: Upgraded to saucy on 2013-10-18 (33 days ago)

Revision history for this message
Andreas Jonsson (sonofjon) wrote :
Revision history for this message
Andreas Jonsson (sonofjon) wrote :

Running Ubuntu 13.10 and Android 4.3.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

affects: nautilus (Ubuntu) → gvfs (Ubuntu)
Changed in gvfs (Ubuntu):
importance: Undecided → Low
Revision history for this message
Andreas Jonsson (sonofjon) wrote :
Changed in gvfs (Ubuntu):
assignee: nobody → Philip Langdale (langdalepl)
status: New → Fix Committed
Changed in gvfs:
importance: Unknown → Medium
status: Unknown → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gvfs - 1.19.4+git20140116-0ubuntu1

---------------
gvfs (1.19.4+git20140116-0ubuntu1) trusty; urgency=medium

  * New upstream release:
    - Fix MTP backend crashes (LP: #1253187)
    - Update to current git head to fix gphoto test with current libgphoto2
      2.5.3.
  * debian/control.in: Bump libsmbclient build dep as per upstream
    configure.ac.
  * Drop 05_shared_libdaemon.patch, fixed upstream.
  * debian/rules: Drop -Wl,-z,defs to fix build.
 -- Martin Pitt <email address hidden> Thu, 16 Jan 2014 09:39:54 +0100

Changed in gvfs (Ubuntu):
status: Fix Committed → Fix Released
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.