View Single Post
Old 01-03-2014, 03:50 PM   #6
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,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
We might have a vocabulary problem.

By "content server" I mean connecting from CC to calibre via "content server". I do not mean connecting via a cable. CC has never supported directly seeing books (or anything else) that were transferred by cable. Instead they are added only if the "scan for new books" setting is enabled and if CC successfully connects as a wireless device.

According to the debug logs you sent me, calibre did not receive a request to connect as a wireless device. CC claims to have sent one, which implies that there is a firewall or antivirus problem. The "content server" log you sent me is a connection via cable, which as I noted above doesn't involve CC at all.

Please try the following:

1) Start calibre in debug mode.
2) Start CC
3) In CC's Wireless Device Settings, press "Use Default". This should show as "automatic" in settings.
4) In CC, attempt to connect as a wireless device.
5) Send me the calibre debug log.

You should see something like the following in the debug log:
Code:
SMART_DEV (   1.90:  1.006) run All IP addresses {'{846EE342-7039-11DE-9D20-806E6F6E6963}': [{'broadcast': '127.255.255.255', 'netmask': '255.0.0.0', 'addr': '127.0.0.1'}], '{079F0E0A-8581-485F-BE57-EE3E77DEA19E}': [{'addr': '169.254.227.25
3'}], '{850AA568-3020-4789-B1B0-2058B85B1B38}': [{'broadcast': '192.168.120.255', 'netmask': '255.255.255.0', 'addr': '192.168.120.38'}], '{C157F596-819B-4E9C-9EA1-EAE7E678AB83}': [{'broadcast': '192.168.56.255', 'netmask': '255.255.255.0', 'addr': '192.168.56.1'}]}
SMART_DEV (  39.43: 37.517) run received broadcast ('localhost', ('192.168.120.6', 54982)) calibre wireless device client (on WALLABY);8080,9090
SMART_DEV (  43.51:  4.056) run attempt to open device socket
SMART_DEV (  45.16:  1.638) reset
SMART_DEV (  45.17:  0.000) set_progress_reporter
SMART_DEV (  45.21:  0.000) open
SMART_DEV (  45.22:  0.000) _call_client GET_INITIALIZATION_INFO wfr True
Specifically, you should see the line "run received broadcast" followed by GET_INITIALIZATION_INFO. If you do not, then something (a firewall or A/V) is preventing CC from talking to calibre.

If you do not see the "run received broadcast" etc lines then you can test if a third-party firewall of A/V package is preventing CC from talking to calibre by booting windows in Safe Mode with Networking. In safe mode, start calibre and attempt to connect CC. If this works then it is certain that something on your computer is blocking CC.
chaley is offline   Reply With Quote