OpenSession failed: LIBUSB_ERROR_TIMEOUT about go-mtpfs HOT 7 CLOSED

USB can get a bit wonky when the last connection wasn't closed correctly. I've added some retry logic to the master branch. can you try again?

from go-mtpfs.

Hi hanwen.
Thanks for a fix but it seems it doesn't work.
Now I'm getting
2013/02/07 16:38:40 Configure failed: OpenSession after reset: LIBUSB_ERROR_TIMEOUT
I'm going to restart my computer to ensure that nothing is using my device and there are no previous connections closed improperly. Will notify you soon.

from go-mtpfs.

There is also a -usb-timeout flag now. You can set that to a higher value,
it's 2000 ms (2 seconds) right now.

On Thu, Feb 7, 2013 at 3:45 PM, mykhaylo- [email protected] wrote:

Hi hanwen.
Thanks for a fix but it seems it doesn't work.
Now I'm getting
2013/02/07 16:38:40 Configure failed: OpenSession after reset:
LIBUSB_ERROR_TIMEOUT
I'm going to restart my computer to ensure that nothing is using my device
and there are no previous connections closed improperly. Will notify you
soon.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-13238643.

Han-Wen Nienhuys - [email protected] - http://www.xs4all.nl/~hanwen

from go-mtpfs.

Working after restart! Now terminal says

2013/02/07 16:50:01 starting FUSE unknown

But process wasn't go to background. Does it mean that when I close terminal, go-mtpfs will terminate and device will be unmounted?
Also in dmesg I noticed

 [  126.126175] usb 3-1: usbfs: process 3026 (go-mtpfs) did not claim interface 0 before use

Is it good or bad?
Thanks again.

from go-mtpfs.

On Thu, Feb 7, 2013 at 3:57 PM, mykhaylo- [email protected] wrote:

Working after restart!

Normally, you can just un- and replug the USB cable.

Now terminal says

2013/02/07 16:50:01 starting FUSE unknown

But process wasn't go to background. Does it mean that when I close
terminal, go-mtpfs will terminate and device will be unmounted?

run it with &

Also in dmesg I noticed

[ 126.126175] usb 3-1: usbfs: process 3026 (go-mtpfs) did not claim interface 0 before use

Is it good or bad?

A small bug. I'll have a look at it later.

Thanks again.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-13239233.

Han-Wen Nienhuys - [email protected] - http://www.xs4all.nl/~hanwen

from go-mtpfs.

Great. Thanks.
So, closing this ticket.
Thanks again.

from go-mtpfs.

If fixed the " process 3026 (go-mtpfs) did not claim interface 0 before use" problem.

from go-mtpfs.