View Single Post
Old 01-04-2015, 02:12 AM   #10
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,452
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by mathuin View Post
Tried the wireless transfer again, and couldn't back-arrow out while the "Syncing with Calibre..." window was up. Waited a long time (didn't check) and it eventually disappeared and was replaced with the connection error box I've mentioned before. Hit OK, then hit back arrow twice, then restarted the app, and was able to connect again. Having a cancel button on the "Syncing with Calibre..." window would be nice.
Yea, I can see why you would want it in this case. The problem we face is that it would be very easy to corrupt the database, and there isn't any way to tell calibre that CC wants to stop short of forcing a disconnect. I will look for some way to reliably stop the transfers.

It is good that connections worked again without power-cycling your device. That means that the OS (Android) recovered all the resources when CC died and cleaned up after itself, exactly as it is supposed to do.
Quote:
Transfer with the content server was unsuccessful.
That is interesting. That says with certainty that the problem is not in calibre's wireless device driver or protocol, because the driver isn't used for content server connections. It also says with high probability that the problem is not in CC because the HTTP file transfer code comes (unmodified) from the Apache project. One way to check the latter point for sure: attempt a transfer using Chrome (or whatever web browser you have), which will entirely eliminate CC from the transfer process. In any event, it is looking more and more like the problem is in your device or in your network somewhere.

Note: the content server logs are available in Preferences / Sharing over the net.
Quote:
Some interesting output on the calibre xterm, though:

libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
timed out

Traceback (most recent call last):
File "site-packages/calibre/gui2/device.py", line 87, in run
File "site-packages/calibre/gui2/device.py", line 584, in _upload_books
File "site-packages/calibre/devices/smart_device_app/driver.py", line 50, in _synchronizer
File "site-packages/calibre/devices/smart_device_app/driver.py", line 1445, in upload_books
File "site-packages/calibre/devices/smart_device_app/driver.py", line 683, in _put_file
File "site-packages/calibre/devices/smart_device_app/driver.py", line 574, in _send_byte_string
timeout: timed out
This is left over from the transfer attempt
Quote:
Syntax Error: Couldn't find trailer dictionary
Syntax Error: Couldn't find trailer dictionary
Syntax Error: Couldn't read xref table
pdfinfo errored out with return code: 1
Traceback (most recent call last):
File "site-packages/calibre/customize/ui.py", line 349, in get_file_type_metadata
File "site-packages/calibre/customize/builtins.py", line 325, in get_metadata
File "site-packages/calibre/ebooks/metadata/pdf.py", line 101, in get_metadata
ValueError: Could not read info dict from PDF
This looks like a PDF book was added to calibre, and calibre failed to read the metadata inside the PDF.
Quote:
Traceback (most recent call last):
File "site-packages/calibre/devices/smart_device_app/driver.py", line 612, in _call_client
File "site-packages/calibre/devices/smart_device_app/driver.py", line 654, in _receive_from_client
ControlError: Device responded with incorrect information
This is probably CC disconnecting. We made a small mistake when we designed the wireless device protocol, leaving out a command to tell calibre when the device wants to disconnect. Instead we simply close the connection, which calibre detects as "incorrect information" when it attempts to poll the device.
chaley is offline   Reply With Quote