-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conflicts with GVFS for access to MTP device #59
Comments
I don't know, maybe filing bug in gnome bugtracker will help. They might mount vfs lazily on first access or something. |
Maybe it could be solved by message box with "stop" buttons ;) |
I think that I might have this same problem as well. My problem is that I can't disable MTP as soon as I plug the phone (Samsung Galaxy S4) in, so when I try to run the program it complains about MTP already running. I've been trying to figure out how to disable MTP on the phone side, but so far no luck. :/ I tried killing gvfs-mtp and then running the program, but got this error message: vector::_M_range_check: __n (which is 0) >= this->size() (which is 0) and then a blank window. |
Try run it once again after this error |
No dice. It doesn't seem to be detecting the device at all once gvfsd-mtp stops running, hence the blank window in AFT. If I leave the phone plugged plugged in, then it reconnects and it's in MTP mode once more. I should also note that I get the same "Device is busy, maybe another process is using it. Close other MTP applications and restart Android File Transfer." message when the phone is in PTP mode. Ugh. If only my music files didn't have spaces in the names. I'd just use good old AWK+adb to handle everything in terminal. |
If AFS could not find device it shows "device not found" dialog. It looks like your DE/udev keep restarting gvfsd-mtp. You could try uninstall it, if you'd prefer. But before that, can you help me debugging this range check exception? |
Sure thing. What do you need me to do? |
clone the latest master from git and
then type the following commands in gdb console:
then breakpoint triggered, type:
finally you will get all c++ exception after device detection, like range_check you mentioned. type |
Here's the output for the exceptions. On 06/01/2015 09:27 AM, Vladimir wrote:
#0 0x00007ffff693e0ed in __cxa_throw () |
You might forgot to run program after setting breakpoint in main window or run it more than once. Please note that you have to run program, then type "catch throw" after first breakpoint triggers. This is needed to skip exception you sent me. :) |
How about now? On 06/05/2015 03:03 AM, Vladimir wrote:
(gdb) b mainwindow.cpp:137 ##################################################################### ##################################################################### (gdb) b mainwindow.cpp:132 Breakpoint 1, MainWindow::showEvent (this=0x7fffffffdd80) ###################################################################### #0 0x00007ffff693e0ed in cxa_throw () |
may I ask you to skip this exception (with 'c' command), and post here when range error appeared (I think it will be the next exception) |
Here ya go... On 06/08/2015 08:25 AM, Vladimir wrote:
(gdb) b mainwindow.cpp:120 Breakpoint 1, MainWindow::showEvent (this=0x7fffffffdd80) ################################################################################ #0 0x00007ffff693e0ed in __cxa_throw () |
Could you check with the latest version? There were a lot of protocol/usb-related fixes. |
When I try to use AFT on a GNOME system, GVFS "steals" the mount and denies AFT access unless I kill gvfsd and all dependent processes. Is there any way to work around this?
The text was updated successfully, but these errors were encountered: