[Bug 1160847] Re: please add an option to inhibit gvfs mtp mounts
The problem here is that the USB Vendor and DeviceID are the same in Ubuntu Touch and in android (we use the same kernel so the device identifies itself the same way). Unlike android Ubuntu Touch doesn't ship and MTP userspace bits which makes the mount fail. I would expect gvfs to notice that and not try again as long as there was no reconnect but instead it fires a new mount attempt every minute (resulting in a new error popup). gvfs should definitely not try mounting over and over once it knows there is no way to mount as long as there was no physical reconnect. We can't just rip out the device IDs from the rules file as this would break all devices of the same model using android here. Thenaks for the info that MTP does not interfere with adb, so in case we decide we will use it (this is not clear yet, we might decide to just connect as USB mass storage for more convenient device access) it would go away. I still think teh behavior is a bug though. Can gvfs be told to not attempt constant mounting in a loop please ? An USB ID is not enough to identify if the MTP protocol is supported or not. A single mount attempt should be enough to notice if there is userspace support. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1160847 Title: please add an option to inhibit gvfs mtp mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1160847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1160847] Re: please add an option to inhibit gvfs mtp mounts
The MTP monitor in gvfs looks for usb devices with the IS_MTP flag set in the udev info. This is controlled by the 69-libmtp.rules file, so if Ubuntu Touch devices shouldn't be identified as having MTP, then the appropriate change should be made to the rules file. There is no conflict between mtp and adb on normal Android devices. I use both all the time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1160847 Title: please add an option to inhibit gvfs mtp mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1160847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1160847] Re: please add an option to inhibit gvfs mtp mounts
the mtp functionallity seems to be defined in /lib/udev/rules.d/69-libmtp.rules, a quick and hackish workaround for affected people using Ubuntu Touch would be to move this rules file out of /lib/udev/rules.d/ (note that this indeed suppresses all mtp support) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1160847 Title: please add an option to inhibit gvfs mtp mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1160847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1160847] Re: please add an option to inhibit gvfs mtp mounts
so analyzing this a bit deeper, it actually does not have anything to do with adb but with the fact that gvfs assumes that if an USB device registers with: Product: Android Manufacturer: Android (seen in dmesg) gvfs blindly assumes there is mtp support on the other side ... Ubuntu Touch currently does not ship any mtp support which causes the gvfs mount to fail and to retry over and over (once every 60 seconds). we should: a) not make gvfs try to mount at all if we detect an adb connection since then it is clear that we are in developer or flashing mode. b) probably make gvfs not try to remount at all if it already knows there is no mtp on the responding side c) at some point ship mtp support on the ubuntu touch images though it has to be researched if this interferes with adb which we require for flashing, debugging and development currently. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1160847 Title: please add an option to inhibit gvfs mtp mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1160847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1160847] Re: please add an option to inhibit gvfs mtp mounts
Thanks ogra, we have indeed a "known issue" there and not specific to the phablet scripts, our mtp stack doesn't handle "conflicting" access well. That's happening as well with mtp music players where rhythmbox/gvfs conflict in a similar way. One thing we could do is probably to not automount the devices when plugged (e.g wait for the user to click on the icon), that would be only a workaround though (you would still get issues if you run e.g a music player that detects your device/lists the songs included on it). It would also somewhat be an user experience regression because it would add an extra step for normal users (most users probably don't run the phablet script but rather want to be able to copy files from/to their device) ** Changed in: gvfs (Ubuntu) Status: New => Confirmed ** Changed in: gvfs (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1160847 Title: please add an option to inhibit gvfs mtp mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1160847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
