error connecing wirelessly and sending book

[Purple Lady]

I had to correct something in a book and used Calibre edit book to fix it. I deleted the book from CC before connecting and sent the book. I then saw that my fix to the book didn't work, so I disconnected and deleted the book in CC again. When I then connected wirelessly again and tried to send the book I got an error. I exited CC and tried again and got same error so I forced stopped and still had an error. I'll send both CC and Calibre logs.

calibre, version 2.5.0
ERROR: Error: Error communicating with device

[Errno 10053] An established connection was aborted by the software in your host machine

Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 87, in run
File "site-packages\calibre\gui2\device.py", line 583, in _upload_books
File "site-packages\calibre\devices\smart_device_app\driver.p y", line 50, in _synchronizer
File "site-packages\calibre\devices\smart_device_app\driver.p y", line 1425, in upload_books
File "site-packages\calibre\devices\smart_device_app\driver.p y", line 681, in _put_file
File "site-packages\calibre\devices\smart_device_app\driver.p y", line 572, in _send_byte_string
error: [Errno 10053] An established connection was aborted by the software in your host machine

Edit: I just restarted Calibre and it works now. I have seen this problem before.

[chaley]

Hmmm... The error message says that something on your calibre computer cut the connection. I wonder if a "threat detector" in your AV or firewall is being triggered by the traffic. The CC/calibre connection sequence is a bit unusual, consisting of UDP broadcasts followed by a TCP connection. A rapid series of this sequence could be considered suspicious.

If you are running some kind of firewall on your device then it could be doing the same thing.

I realize I am grasping at straws, but I don't have any other ideas.

[chaley]

BTW: the CC debug log you sent was from March.

My guess is you picked it up from the CC book directory instead of the CC application directory. That has happened before. I should have deleted any old log when we moved it.

[Purple Lady]

I sent you the correct debug log. and deleted the old one. I sent it manually because sending it thru CC doesn't work with k9 email and I never use my gmail email address so I don't use the Gmail app.

I am not running a firewall on my device. When my tech support gets home and gets some sleep I'll have him check the firewall to see if he sees anything there. He was at work all night for a release that won't even be used right away.

[chaley]

Originally Posted by Purple Lady

I sent you the correct debug log. and deleted the old one. I sent it manually because sending it thru CC doesn't work with k9 email and I never use my gmail email address so I don't use the Gmail app.

Thanks. I think I have found the problem.

Is there any chance that the file was still open in the reader app when you deleted it? I ask because Android told CC that it could not overwrite the file after it was deleted, which means that the file was still open somewhere and not really gone.

[Purple Lady]

Originally Posted by chaley

Thanks. I think I have found the problem.

Is there any chance that the file was still open in the reader app when you deleted it? I ask because Android told CC that it could not overwrite the file after it was deleted, which means that the file was still open somewhere and not really gone.

It shouldn't have been still open. I opened it in Moon+ and used the back button to get back CC so it should have closed. I hit the back button pretty quickly so is it possibly a delay in closing it? Also, if it was still open, why would shutting Calibre down and bringing it back up fix the problem? Is it possible for Calibre to have it held somehow? I've had this problem before and tried to recreate it in the past but couldn't. It just happens when it happens.

[chaley]

Originally Posted by Purple Lady

It shouldn't have been still open. I opened it in Moon+ and used the back button to get back CC so it should have closed. I hit the back button pretty quickly so is it possibly a delay in closing it? Also, if it was still open, why would shutting Calibre down and bringing it back up fix the problem? Is it possible for Calibre to have it held somehow? I've had this problem before and tried to recreate it in the past but couldn't. It just happens when it happens.

Like you, I can't see why closing calibre would have any effect at all on it. Closing CC might, but you did that and it made no never mind. Perhaps it is a "time passes" sort of thing. Some resource needed to be purged.

Question: I have set up moon+ so the back button will "Close moon+". Is that what you have?

[Purple Lady]

Originally Posted by chaley

Like you, I can't see why closing calibre would have any effect at all on it. Closing CC might, but you did that and it made no never mind. Perhaps it is a "time passes" sort of thing. Some resource needed to be purged.

Question: I have set up moon+ so the back button will "Close moon+". Is that what you have?

I have it set to Close Moon+ as well.

Whenever I have encountered this problem before it's always been the same - I want to fix a book so I delete it in CC, fix the book in Calibre, connect wireless and send the book, see that it isn't fixed, use the back button to CC, disconnect, delete it in CC ... and again and again if I don't fix it properly. I think by the 2nd or 3rd time I don't fix it comes up I'm hitting those buttons pretty quickly.