Bug#928058: gvfs-backends: Bogus MTP errors? Everything works but errors pop up. Occurs in XFCE and CINNAMON but not in GNOME
aPpYe
appye at yahoo.com
Sat Apr 27 08:02:44 BST 2019
Package: gvfs-backends
Version: 1.38.1-3
Severity: important
Dear Maintainer,
* What led up to the situation?
I am testing the Cinnamon desktop version of Debian.
I plugged in my android phone to browse and manipulate
the filesystem.
Using a Samsung Galaxy S7 as an example, upon plugging in
the device, before enabling MTP, I see the following error:
Unable to open folder for SAMSUNG Android
Cache invalid, retry (internally handled)
Once I enable MTP on a device, the following error also
appears:
Count not display "mtp://SAMSUNG_SAMSUNG_Android_98545a76/"
Error: No such interface "org.gtk.vfs.Mount" on object at
path /org/gtk/vfs/mount/1
Please select another viewer and try again.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried this on a variety of different Android devices,
and a couple of different laptops and a VM.
* What was the outcome of this action?
Similar behavior was exhibited in all situations.
* What outcome did you expect instead?
I expect to be able to browse and manipulate a filesytem
over MTP without receiving these error messages.
* NOTES:
If running MATE, the cache error does not appear, but the
mtp:// error does appear.
If running GNOME, no errors appear.
In all cases, I am able to browse and manipulate the
filesystem without issue, regardless of whether or not I
acknowledge the error messages.
More details can be found in the original form post here:
http://forums.debian.net/viewtopic.php?f=19&t=141683
It was here where it was suggested to me to file a bug
against gvfs-backends.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gvfs-backends depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii gvfs 1.38.1-3
ii gvfs-common 1.38.1-3
ii gvfs-daemons 1.38.1-3
ii gvfs-libs 1.38.1-3
ii libarchive13 3.3.3-4
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libavahi-glib1 0.7-4+b1
ii libc6 2.28-8
ii libcdio-cdda2 10.2+0.94+2-4
ii libcdio-paranoia2 10.2+0.94+2-4
ii libcdio18 2.0.0-2
ii libgcrypt20 1.8.4-5
ii libgdata22 0.17.9-3
ii libglib2.0-0 2.58.3-1
ii libgoa-1.0-0b 3.30.1-2
ii libgphoto2-6 2.5.22-3
ii libgphoto2-port12 2.5.22-3
ii libgudev-1.0-0 232-2
ii libimobiledevice6 1.2.1~git20181030.92c5462-1
ii libmtp9 1.1.16-2
ii libnfs12 3.0.0-2
ii libplist3 2.0.1~git20190104.3f96731-1
ii libpolkit-gobject-1-0 0.105-25
ii libsmbclient 2:4.9.5+dfsg-3
ii libsoup2.4-1 2.64.2-2
ii libusb-1.0-0 2:1.0.22-2
ii libxml2 2.9.4+dfsg1-7+b3
ii psmisc 23.2-1
Versions of packages gvfs-backends recommends:
ii gnome-keyring 3.28.2-5
Versions of packages gvfs-backends suggests:
ii bluez-obexd 5.50-1
pn samba-common <none>
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list