Bug#882213: gvfs-fuse: MTP device still visible after disconnecting

[Jérémy Viès]

It only happens on stretch with backports enabled.
It seems related to a different behavior of systemd 237 vs 232 that is in
vanilla stretch.

I've backported the patch on my 2 systems, and have seen no regression
until now... but I didn't made a lot of tests !

Regards,

On Thu, 5 Apr 2018 10:43:24 +0100 Simon McVittie  wrote:
> On Wed, 04 Apr 2018 at 21:06:01 +0200, Jérémy Viès wrote:
> > The fixes for gnome-3-22 has also been posted on gnome git repository.
> > Can you backport the fix to gvfs 1.30, used by gnome 3.22 that are on
stretch ?
>
> Maybe. It depends how serious the bug is and how intrusive the fixes are:
> introducing a regression of equal or greater severity would be worse than
> leaving this bug open.
>
> All the reports of this issue that had version information were in
> buster/sid or in a sid-based Debian derivative. Can it be reproduced on
> a pure stretch system, or on a stretch system with specified backports,
> perhaps udev and/or the kernel?
>
> smcv
>
>

Bug#882213: gvfs-fuse: MTP device still visible after disconnecting

[Simon McVittie]

On Wed, 04 Apr 2018 at 21:06:01 +0200, Jérémy Viès wrote:
> The fixes for gnome-3-22 has also been posted on gnome git repository.
> Can you backport the fix to gvfs 1.30, used by gnome 3.22 that are on stretch 
> ?

Maybe. It depends how serious the bug is and how intrusive the fixes are:
introducing a regression of equal or greater severity would be worse than
leaving this bug open.

All the reports of this issue that had version information were in
buster/sid or in a sid-based Debian derivative. Can it be reproduced on
a pure stretch system, or on a stretch system with specified backports,
perhaps udev and/or the kernel?

smcv

Bug#882213: gvfs-fuse: MTP device still visible after disconnecting

[Jérémy Viès]

The fixes for gnome-3-22 has also been posted on gnome git repository.
Can you backport the fix to gvfs 1.30, used by gnome 3.22 that are on
stretch ?

https://github.com/GNOME/gvfs/commits/gnome-3-22

Thx a lot,
Jérémy

On Tue, 3 Apr 2018 12:03:36 +0100 Simon McVittie  wrote:
> Version: 1.35.90-1
>
> On Mon, 20 Nov 2017 at 11:20:10 +0100, Michal M. wrote:
> >  - Unmount your device, disconnect USB cable. Device is removed, but
item is
> > still visible in "Devices" section. It's dead item, not possible to
remove it
> > or mount/unmount
>
> This is believed to have been fixed in gvfs 1.35 (see #882353, #883425).
>
> smcv
>
>

Bug#882213: gvfs-fuse: MTP device still visible after disconnecting

[Simon John]

Seeing this too on Buster/Sid, in fact when swapping my phone from
charge-only to disk mode, I end up with two devices staying around when
I unplug the phone.

Reboot is the only way I can get rid of it - restarting gnome-shell
doesn't help, nor does logging out/in again.

Bug#882213: gvfs-fuse: MTP device still visible after disconnecting

[Michal M.]

Package: gvfs-fuse
Version: 1.34.1-1+b1
Severity: normal

Dear Maintainer,

To reproduce bug:
 - connect any MTP enabled Android Phone to USB
 - run any file manager (Nautilus and Nemo tested). You will see your MTP
device visible in "Devices" section at te left side of file manager window
 - Unmount your device, disconnect USB cable. Device is removed, but item is
still visible in "Devices" section. It's dead item, not possible to remove it
or mount/unmount
 - Connect device to USB again. New item added to "Devices" view.

Multiple connecting/disconnecting devices causes multiple dead items, which is
pretty annoying. I need to reboot system to get them removed.

It seems to be ok when connecting mass storage device (like usb disk, pendrive,
etc), so bug is related to mtp only.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-0.slh.2-aptosid-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gvfs-fuse depends on:
ii  fuse  2.9.7-1
ii  gvfs  1.34.1-1+b1
ii  libc6 2.25-1
ii  libfuse2  2.9.7-1
ii  libglib2.0-0  2.54.2-1

gvfs-fuse recommends no packages.

gvfs-fuse suggests no packages.

-- no debconf information