After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 734770 - MTP harassment
MTP harassment
Status: RESOLVED INCOMPLETE
Product: gvfs
Classification: Core
Component: mtp backend
unspecified
Other Linux
: Normal major
: ---
Assigned To: Philip Langdale
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2014-08-14 08:08 UTC by Vadim Peretokin
Modified: 2016-04-15 15:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vadim Peretokin 2014-08-14 08:08:36 UTC 
I plugged my Android 4.4.4 device in to charge, and it was locked by a pattern. Files kept trying to mount it, spamming me with a dialog each time. The amount of dialogs between the spam increased until it became unbearable, as seen in the screencast here: https://dl.dropboxusercontent.com/u/84880/MTP%20harassment.mp4.
Comment 1 Bastien Nocera 2014-11-02 15:29:36 UTC 
This is probably a bug in gvfs. Can you still reproduce this with a newer gvfs (version 1.22.1 is the latest for GNOME 3.14).
Comment 2 Philip Langdale 2014-11-02 16:15:06 UTC 
The problem is not related to the device being locked. A locked device can be mounted (it just appears to be empty until it is unlocked). I think the source of the problem is unlikely to be gvfs - gvfs doesn't contain the logic that attempts mounts - it just does what it's told. Any attempt to access a gvfs uri will trigger a mount attempt. Perhaps some utility is monitoring devices and attempting to resolve them in some way. We've seen Nautilus do this in the past but not like this, and I'll believe Bastien that it's probably not Nautilus this time.

Did you change the device action to 'Nothing' instead of 'Open window' or whatever it might be? That would be the first thing to try - if that works then the issue is that it's trying too hard - but I'm pretty sure that code path only tries once and then gives up.

What's your device? What firmware? OEM, Cyanogen? etc.