I've tried a live ubuntu 16.04.5 LTS desktop 64 and works perfectly. The
results of dpkg -s gvfs on the working ubuntu is:

Package: gvfs
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 622
Maintainer: Ubuntu Developers <[email protected]>
Architecture: amd64
Multi-Arch: same
Version: 1.28.2-1ubuntu1~16.04.2
Depends: libc6 (>= 2.14), libglib2.0-0 (>= 2.45.7), gvfs-daemons (>= 
1.28.2-1ubuntu1~16.04.2), gvfs-daemons (<< 1.28.2-1ubuntu1~16.04.2.1~), 
gvfs-libs (= 1.28.2-1ubuntu1~16.04.2), gvfs-common (= 1.28.2-1ubuntu1~16.04.2)
Suggests: gvfs-backends
Description: userspace virtual filesystem - GIO module
 gvfs is a userspace virtual filesystem where mounts run as separate
 processes which you talk to via D-Bus. It also contains a gio module
 that seamlessly adds gvfs support to all applications using the gio
 API. It also supports exposing the gvfs mounts to non-gio applications
 using fuse.
 .
 This package contains the GIO module that lets applications use gvfs
 mounts.
Homepage: https://wiki.gnome.org/Projects/gvfs
Original-Maintainer: Debian GNOME Maintainers 
<[email protected]>

The dpkg -s gvfs in the not working 18.04.1 LTS:

Package: gvfs
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 368
Maintainer: Ubuntu Developers <[email protected]>
Architecture: amd64
Multi-Arch: same
Version: 1.36.1-0ubuntu1.2
Depends: libc6 (>= 2.14), libglib2.0-0 (>= 2.49.3), gvfs-daemons (>= 
1.36.1-0ubuntu1.2), gvfs-daemons (<< 1.36.1-0ubuntu1.2.1~), gvfs-libs (= 
1.36.1-0ubuntu1.2), gvfs-common (= 1.36.1-0ubuntu1.2)
Suggests: gvfs-backends
Description: userspace virtual filesystem - GIO module
 gvfs is a userspace virtual filesystem where mounts run as separate
 processes which you talk to via D-Bus. It also contains a gio module
 that seamlessly adds gvfs support to all applications using the gio
 API. It also supports exposing the gvfs mounts to non-gio applications
 using fuse.
 .
 This package contains the GIO module that lets applications use gvfs
 mounts.
Homepage: https://wiki.gnome.org/Projects/gvfs
Original-Maintainer: Debian GNOME Maintainers 
<[email protected]>

-- 
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/1792085

Title:
  MTP no more working on Bionic

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/<MTP-FOLDER>".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to