Your message dated Fri, 13 Mar 2015 09:35:55 +0100
with message-id <[email protected]>
and subject line done
has caused the Debian Bug report #773627,
regarding gvfs-automount makes devices invisible to fdisk
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
773627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773627
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: gvfs
Version: 1.22.2-1
Severity: minor
Dear Maintainer,
drag-and-drop used to be not workable from gvfs-automounted usb-media, both
with GNOME
and Cinnamon. XFCE-desktop does not show such strange behaviour. This is fixed
already
again, but the problem remains, that fdisk does not see storage-devices, that
were
automounted. When you decide, not to automount them, they are not visible
either. It's a
problem.
When dragging files from automounted media into a terminal-window, they look
like this:
'/run/user/1003/gvfs/mtp:host=%5Busb%3A001%2C006%5D/your-local-path'
- -- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.7-ckt2edtr (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages gvfs depends on:
ii gvfs-common 1.22.2-1
ii gvfs-daemons 1.22.2-1
ii gvfs-libs 1.22.2-1
ii libc6 2.19-13
ii libglib2.0-0 2.42.1-1
ii libudev1 215-7
gvfs recommends no packages.
Versions of packages gvfs suggests:
ii gvfs-backends 1.22.2-1
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlSWWXsACgkQ5+rBHyUt5wspAwCglEdIW4ohUJEHrQEymrQAhV0f
DpwAn0BXCI4SJ92+HeWWwwUUOQWsZD72
=e0Ba
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Today I rechecked on this issue and it is obviously resolved.
I did not notice any related GNOME-updates, that might have fixed this, so
maybe it was
something like a bug in glibc, or similar, something more basic.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlUCoXQACgkQ5+rBHyUt5wtW9ACfblAvLinUGoAP1aHFccjWolu5
jvEAnA/m5THBTSSGgtz6A3pQ+oASphlZ
=bgEK
-----END PGP SIGNATURE-----
--- End Message ---
