Nokia Lumia 620 (WP8) fails to mount reliably via gvfs-mtp in nautilus
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
New
|
Undecided
|
Unassigned | ||
gvfs |
Fix Released
|
Medium
|
|||
gvfs (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
nautilus (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Summary: You have to run mtp-detect in terminal until you get output similar to the excerpt in the steps to reproduce section, then you can connect via nautilus as usual.
-----
I just got a Nokia Lumia 620 as a backup phone. I'd say I can mount my Nexus 4 reliably with Ubuntu via nautilus using gvfs-mtp. Users with Android devices like the Nexus 4 still get error messages on a regularly basis of the device not being able to mount, but replugging the device mostly fixes the issue.
However, the experience with the Lumia 620 is far worse (the desktop sometimes freezes) and the workaround I found to get the device to work very crude.
I was prompted with a apport-collector window when nautilus froze during testing and send a report (this happend twice), but it didn't take me to Launchpad to open a report. I can also seen no bug regarding that topic that I am subscribed to.
The Lumia 620 itself was added to libmtp with this report: http://
## Steps to reproduce:
1. Reboot (or cold boot) computer and phone. Login to computers destop and unlock the phone by entering PIN.
2. Plug the phone via USB into the computer. (Cable works with Nexus 4 or another Android device.) The phone will give a signal that it is connected to the computer.
3. Try to open the phone in Nautilus. My desktop either freezes (cold boot) here or nautilus hangs (reboot).
3.a) If nautilus hangs: Open a terminal with Ctrl+Alt+T and kill nautilus with xkill.
3.b) If your desktop froze: Go to a virtual terminal with Ctrl+Alt+F1.
3.c) If you just get an error message: Open a terminal with Ctrl+Alt+T and go to step 4.
4. Execute 'mtp-detect' (from mtp-tools package) from terminal (either via Dektop or virtual terminal). If you get one of the following messages wait a few seconds and try again.
$ mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=0421 and PID=0661) is a Nokia Nokia Lumia WP8.
Found 1 device(s):
Nokia: Nokia Lumia WP8 (0421:0661) @ bus 2, dev 22
Attempting to connect device(s)
ignoring libusb_
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
---
$ mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=0421 and PID=0661) is a Nokia Nokia Lumia WP8.
Found 1 device(s):
Nokia: Nokia Lumia WP8 (0421:0661) @ bus 2, dev 22
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
---
Repeat this until you get a long list of scrolling text that ends with something similar to this:
MTP-specific device properties:
Friendly name: Windows Phone
Synchroniz
Battery level 74 of 100 (74%)
libmtp supported (playable) filetypes:
Folder
Text file
ISO MPEG-1 Audio Layer 3
Audio Video Interleave
JPEG file
Microsoft Windows Media Audio
Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
Microsoft Windows Media Video
Abstract Album file
Abstract Playlist file
GIF bitmap file
JFIF file
Portable Network Graphics
TIFF bitmap file
BMP bitmap file
MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
MPEG-4 Part 14 Container Format (Audio Emphasis)
DOC file
XLS file
PPT file
OK.
---
5. Go to a virtual terminal and do 'sudo service lightdm restart'. Login again, you hear the phone reconnecting to your computer and should now be able to open your phone in nautilus seeing the phones internal storage and the SD card (if there is) als sub devices.
6. Unplug the phone from the computer and start with step 2 if you want to connect the phone again.
## Additional information
$ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
$ apt-cache policy gvfs gvfs-backends mtp-tools
gvfs:
Installed: 1.18.2-0ubuntu1
Candidate: 1.18.2-0ubuntu1
Version table:
*** 1.18.2-0ubuntu1 0
500 http://
100 /var/lib/
gvfs-backends:
Installed: 1.18.2-0ubuntu1
Candidate: 1.18.2-0ubuntu1
Version table:
*** 1.18.2-0ubuntu1 0
500 http://
100 /var/lib/
mtp-tools:
Installed: 1.1.6-2
Candidate: 1.1.6-2
Version table:
*** 1.1.6-2 0
500 http://
100 /var/lib/
description: | updated |
description: | updated |
Changed in gvfs: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
description: | updated |
Changed in gvfs: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in gvfs: | |
status: | New → Incomplete |
Changed in gvfs: | |
status: | Incomplete → Fix Released |
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.