Public bug reported:

My Nokia 6.1 phone is properly autodetected, and I can fetch files from it fine 
via
the default ubuntu gui (using gvfs etc).

However, running gmtp fails.  To diagnose this I tried running mtp-detect.
This fails with

dank@thinky:~$ mtp-detect
libmtp version: 1.1.16

Listing raw device(s)
Device 0 (VID=2e04 and PID=c025) is a Nokia 6.
   Found 1 device(s):
   Nokia: 6 (2e04:c025) @ bus 3, dev 35
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to 
initialize device
Unable to open raw device 0
OK.

As described in 
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/comments/40
killing gvfs-gphoto2-volume-monitor let mtd-detect and gmtd work properly.

Is the clash expected?

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gvfs-backends 1.40.1-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 12 15:21:27 2019
InstallationDate: Installed on 2017-04-29 (743 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gvfs
UpgradeStatus: Upgraded to disco on 2019-05-12 (0 days ago)

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


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1828748

Title:
  gmtp can't connect to phone while gvfs-gphoto2-volume-monitor running

Status in gvfs package in Ubuntu:
  New

Bug description:
  My Nokia 6.1 phone is properly autodetected, and I can fetch files from it 
fine via
  the default ubuntu gui (using gvfs etc).

  However, running gmtp fails.  To diagnose this I tried running mtp-detect.
  This fails with

  dank@thinky:~$ mtp-detect
  libmtp version: 1.1.16

  Listing raw device(s)
  Device 0 (VID=2e04 and PID=c025) is a Nokia 6.
     Found 1 device(s):
     Nokia: 6 (2e04:c025) @ bus 3, dev 35
  Attempting to connect device(s)
  error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to 
initialize device
  Unable to open raw device 0
  OK.

  As described in 
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/comments/40
  killing gvfs-gphoto2-volume-monitor let mtd-detect and gmtd work properly.

  Is the clash expected?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gvfs-backends 1.40.1-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 12 15:21:27 2019
  InstallationDate: Installed on 2017-04-29 (743 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to disco on 2019-05-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828748/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to