Buster Android MTP
Posted: 2019-04-20 17:29
Hello, I am unsure what subforum is a good choice for this. I chose development because I am playing with testing.
With Buster's move to stable coming just around the corner, I have been putting together a desktop installation procedure for myself, friends and family. I start with the default Cinnamon desktop as a base and go from there. I have software choices and configs pretty well ironed out. At this point I will pretty much wait until the official announcement of Debian 10 before installing to our machines...
The only thing I have left is MTP and Android connectivity.
I get similar behavior on an LG G2, a Samsung Galaxy s7, and a Motorola Droid Turbo 2 ...
Using my S7 as an example, once I plug a device into a USB port, I get the following prompt:
Unable to open folder for SAMSUNG Android
Cache invalid, retry (internally handled)
If an instance of Nemo (the default Cinnamon file manager) is NOT running, then once I enable MTP, Nemo pops up and shows me the Devices filesystems. If Nemo IS running, whether in the foreground or background, I get one of the following prompts, I have not seen any kind of pattern to it, though I mostly get the second, more specific prompt:
Unable to open a folder for SAMSUNG Android
No such interface "org.gtk.vfs.Mount" on object at path /org/gtk/vfs/mount/1
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.
... In all cases, I am able to browse and manipulate the filesystem without any problems, regardless of whether or not I acknowledge the error prompts. I don't know where to begin with this. I have looked up MTP issues all over the internet and have not found this specific issue. I see a lot of people talking about errors mounting (is MTP ever really "mounted?") and being unable to see the device filesytem at all, etc. None where it seems to just be cosmetic error prompts. I do not (and would like to avoid, if I can) installation of any specific MTP software, as it seems to be handled well enough (except for the errors) with Debian default auto installed choices. Is this specific to Cinnamon? Is it something underlying?
With Buster's move to stable coming just around the corner, I have been putting together a desktop installation procedure for myself, friends and family. I start with the default Cinnamon desktop as a base and go from there. I have software choices and configs pretty well ironed out. At this point I will pretty much wait until the official announcement of Debian 10 before installing to our machines...
The only thing I have left is MTP and Android connectivity.
I get similar behavior on an LG G2, a Samsung Galaxy s7, and a Motorola Droid Turbo 2 ...
Using my S7 as an example, once I plug a device into a USB port, I get the following prompt:
Unable to open folder for SAMSUNG Android
Cache invalid, retry (internally handled)
If an instance of Nemo (the default Cinnamon file manager) is NOT running, then once I enable MTP, Nemo pops up and shows me the Devices filesystems. If Nemo IS running, whether in the foreground or background, I get one of the following prompts, I have not seen any kind of pattern to it, though I mostly get the second, more specific prompt:
Unable to open a folder for SAMSUNG Android
No such interface "org.gtk.vfs.Mount" on object at path /org/gtk/vfs/mount/1
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.
... In all cases, I am able to browse and manipulate the filesystem without any problems, regardless of whether or not I acknowledge the error prompts. I don't know where to begin with this. I have looked up MTP issues all over the internet and have not found this specific issue. I see a lot of people talking about errors mounting (is MTP ever really "mounted?") and being unable to see the device filesytem at all, etc. None where it seems to just be cosmetic error prompts. I do not (and would like to avoid, if I can) installation of any specific MTP software, as it seems to be handled well enough (except for the errors) with Debian default auto installed choices. Is this specific to Cinnamon? Is it something underlying?