MobileRead Forums
Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Software > Calibre > Devices
Reload this Page Calibre freezes when a WIFI connection is established

Notices

Reply
 
Thread Tools Search this Thread
Old 03-18-2017, 11:25 AM   #1
ryt
Junior Member
ryt began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Mar 2017
Device: Kobo Aura One
Calibre freezes when a WIFI connection is established
Hello,

When trying to send a document to my Kobo Aura One, I get the same behavior as exposed in this topic :

https://github.com/koreader/koreader/issues/2540

I'm running under MacOS 10.12.3.

The first guy summarized pretty well the issue:
Steps to reproduce

1. Start wireless server in Calibre. Server starts.
2. Connect Koreader to Calibre wireless. Client says that it is connected.
3. Calibre does not react to established connection, no connected device menus appear, no "On device" column. If you try to do anything related to wireless connection in Calibre (i.e. open "share" menu or try to upload a book), it's UI becomes unresponsive.

Despite this bug, Calibre is a great tool. It's been very practical and user-friendly. Thank you for developing and maintaining it over the years!

Ryt
ryt is offline   Reply With Quote
Old 03-18-2017, 11:32 AM   #2
ryt
Junior Member
ryt began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Mar 2017
Device: Kobo Aura One
Here is the backtrace, I stopped it when it freezed

Spoiler:

* thread #1: tid = 0x56c7, 0x00007fff9f7e4c86 libsystem_kernel.dylib`__psynch_cvwait + 10, stop reason = signal SIGSTOP
frame #0: 0x00007fff9f7e4c86 libsystem_kernel.dylib`__psynch_cvwait + 10
frame #1: 0x00007fff9f8ce96a libsystem_pthread.dylib`_pthread_cond_wait + 712
frame #2: 0x00000001001823e1 Python`PyThread_acquire_lock + 113
frame #3: 0x0000000100187347 Python`lock_PyThread_acquire_lock + 71
frame #4: 0x0000000100148e8f Python`PyEval_EvalFrameEx + 30591
frame #5: 0x0000000100141402 Python`PyEval_EvalCodeEx + 1538
frame #6: 0x00000001000ccb7c Python`function_call + 364
frame #7: 0x00000001000a6f33 Python`PyObject_Call + 99
frame #8: 0x00000001000b4136 Python`instancemethod_call + 182
frame #9: 0x00000001000a6f33 Python`PyObject_Call + 99
frame #10: 0x00000001000a1787 Python`PyObject_CallFunctionObjArgs + 359
frame #11: 0x0000000100148450 Python`PyEval_EvalFrameEx + 27968
frame #12: 0x0000000100141402 Python`PyEval_EvalCodeEx + 1538
frame #13: 0x00000001000ccb7c Python`function_call + 364
frame #14: 0x00000001000a6f33 Python`PyObject_Call + 99
frame #15: 0x00000001001495eb Python`PyEval_EvalFrameEx + 32475
frame #16: 0x0000000100141402 Python`PyEval_EvalCodeEx + 1538
frame #17: 0x000000010014db25 Python`fast_function + 117
frame #18: 0x0000000100148a85 Python`PyEval_EvalFrameEx + 29557
frame #19: 0x0000000100141402 Python`PyEval_EvalCodeEx + 1538
frame #20: 0x000000010014db25 Python`fast_function + 117
frame #21: 0x0000000100148a85 Python`PyEval_EvalFrameEx + 29557
frame #22: 0x0000000100141402 Python`PyEval_EvalCodeEx + 1538
frame #23: 0x00000001000ccb7c Python`function_call + 364
frame #24: 0x00000001000a6f33 Python`PyObject_Call + 99
frame #25: 0x00000001000b4136 Python`instancemethod_call + 182
frame #26: 0x00000001000a6f33 Python`PyObject_Call + 99
frame #27: 0x000000010014d31d Python`PyEval_CallObjectWithKeywords + 93
frame #28: 0x00000001065480e8 QtCore.so`PyQtSlot::call(_object*, _object*) const + 40
frame #29: 0x0000000106547fe5 QtCore.so`PyQtSlot::invoke(void**, _object*, void*, bool) const + 309
frame #30: 0x0000000106548967 QtCore.so`PyQtSlotProxy::unislot(void**) + 103
frame #31: 0x00000001065488e5 QtCore.so`PyQtSlotProxy::qt_metacall(QMetaObject:: Call, int, void**) + 85
frame #32: 0x000000010608dca9 QtCore`QMetaObject::activate(QObject*, int, int, void**) + 2777
frame #33: 0x000000010547ab7a QtWidgets`QMenu::popup(QPoint const&, QAction*) + 314
frame #34: 0x000000010547bafe QtWidgets`QMenu::exec(QPoint const&, QAction*) + 78
frame #35: 0x00000001054bcc44 QtWidgets`___lldb_unnamed_symbol2585$$QtWidgets + 2004
frame #36: 0x00000001054bd854 QtWidgets`___lldb_unnamed_symbol2589$$QtWidgets + 388
frame #37: 0x000000010608dd82 QtCore`QMetaObject::activate(QObject*, int, int, void**) + 2994
frame #38: 0x00000001053f345d QtWidgets`___lldb_unnamed_symbol1130$$QtWidgets + 45
frame #39: 0x00000001053f4091 QtWidgets`QAbstractButton::mousePressEvent(QMouseE vent*) + 337
frame #40: 0x00000001054bcfc0 QtWidgets`QToolButton::mousePressEvent(QMouseEvent *) + 400
frame #41: 0x0000000105347f27 QtWidgets`QWidget::event(QEvent*) + 1607
frame #42: 0x00000001053f3f13 QtWidgets`QAbstractButton::event(QEvent*) + 179
frame #43: 0x00000001054bd6b4 QtWidgets`QToolButton::event(QEvent*) + 324
* frame #44: 0x000000010530942b QtWidgets`QApplicationPrivate::notify_helper(QObje ct*, QEvent*) + 251
frame #45: 0x000000010530cc5d QtWidgets`QApplication::notify(QObject*, QEvent*) + 9421
frame #46: 0x0000000104ffe0cf QtWidgets.so`sipQApplication::notify(QObject*, QEvent*) + 127
frame #47: 0x000000010605d423 QtCore`QCoreApplication::notifyInternal(QObject*, QEvent*) + 115
frame #48: 0x0000000105309dbb QtWidgets`QApplicationPrivate::sendMouseEvent(QWid get*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) + 987
frame #49: 0x0000000105368570 QtWidgets`___lldb_unnamed_symbol622$$QtWidgets + 1200
frame #50: 0x000000010536777f QtWidgets`___lldb_unnamed_symbol617$$QtWidgets + 111
frame #51: 0x000000010530942b QtWidgets`QApplicationPrivate::notify_helper(QObje ct*, QEvent*) + 251
frame #52: 0x000000010530c80e QtWidgets`QApplication::notify(QObject*, QEvent*) + 8318
frame #53: 0x0000000104ffe0cf QtWidgets.so`sipQApplication::notify(QObject*, QEvent*) + 127
frame #54: 0x000000010605d423 QtCore`QCoreApplication::notifyInternal(QObject*, QEvent*) + 115
frame #55: 0x0000000105950b39 QtGui`QGuiApplicationPrivate::processMouseEvent(QW indowSystemInterfacePrivate::MouseEvent*) + 2185
frame #56: 0x000000010594f9c3 QtGui`QGuiApplicationPrivate::processWindowSystemE vent(QWindowSystemInterfacePrivate::WindowSystemEv ent*) + 131
frame #57: 0x000000010593c59a QtGui`QWindowSystemInterface::sendWindowSystemEven ts(QFlags<QEventLoop::ProcessEventsFlag>) + 346
frame #58: 0x000000010c297371 libqcocoa.dylib`___lldb_unnamed_symbol458$$libqcoc oa.dylib + 33
frame #59: 0x00007fff8a17e981 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOU RCE0_PERFORM_FUNCTION__ + 17
frame #60: 0x00007fff8a15fa7d CoreFoundation`__CFRunLoopDoSources0 + 557
frame #61: 0x00007fff8a15ef76 CoreFoundation`__CFRunLoopRun + 934
frame #62: 0x00007fff8a15e974 CoreFoundation`CFRunLoopRunSpecific + 420
frame #63: 0x00007fff896eaa5c HIToolbox`RunCurrentEventLoopInMode + 240
frame #64: 0x00007fff896ea799 HIToolbox`ReceiveNextEventCommon + 184
frame #65: 0x00007fff896ea6c6 HIToolbox`_BlockUntilNextEventMatchingListInModeWi thFilter + 71
frame #66: 0x00007fff87c905b4 AppKit`_DPSNextEvent + 1120
frame #67: 0x00007fff8840ad6b AppKit`-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:deque ue:] + 2789
frame #68: 0x00007fff87c84f35 AppKit`-[NSApplication run] + 926
frame #69: 0x000000010c29625d libqcocoa.dylib`___lldb_unnamed_symbol440$$libqcoc oa.dylib + 2189
frame #70: 0x000000010605ab1d QtCore`QEventLoop::exec(QFlags<QEventLoop::Process EventsFlag>) + 381
frame #71: 0x000000010605d9fa QtCore`QCoreApplication::exec() + 346
frame #72: 0x0000000105032bd0 QtWidgets.so`___lldb_unnamed_symbol6360$$QtWidgets .so + 80
frame #73: 0x0000000100148e8f Python`PyEval_EvalFrameEx + 30591
frame #74: 0x0000000100141402 Python`PyEval_EvalCodeEx + 1538
frame #75: 0x000000010014db25 Python`fast_function + 117
frame #76: 0x0000000100148a85 Python`PyEval_EvalFrameEx + 29557
frame #77: 0x0000000100141402 Python`PyEval_EvalCodeEx + 1538
frame #78: 0x000000010014db25 Python`fast_function + 117
frame #79: 0x0000000100148a85 Python`PyEval_EvalFrameEx + 29557
frame #80: 0x0000000100141402 Python`PyEval_EvalCodeEx + 1538
frame #81: 0x000000010014db25 Python`fast_function + 117
frame #82: 0x0000000100148a85 Python`PyEval_EvalFrameEx + 29557
frame #83: 0x000000010014dbc2 Python`fast_function + 274
frame #84: 0x0000000100148a85 Python`PyEval_EvalFrameEx + 29557
frame #85: 0x0000000100141402 Python`PyEval_EvalCodeEx + 1538
frame #86: 0x00000001000ccb7c Python`function_call + 364
frame #87: 0x00000001000a6f33 Python`PyObject_Call + 99
frame #88: 0x000000010014d31d Python`PyEval_CallObjectWithKeywords + 93
frame #89: 0x00000001000938f5 calibre-launcher.dylib`run + 1221
frame #90: 0x0000000100001dfe calibre`main + 158
frame #91: 0x0000000100001d54 calibre`start + 52
ryt is offline   Reply With Quote
Advert
Old 03-18-2017, 11:33 AM   #3
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 30,950
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
This appears to be a Koreader issue.
Wireless Device Connection works with Calibre Companion (they were designed by the same team )

(WDC is the only remote (network) connection that shows a OnDevice column)
theducks is offline   Reply With Quote
Old 03-18-2017, 11:39 AM   #4
ryt
Junior Member
ryt began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Mar 2017
Device: Kobo Aura One
Thank you theducks for your quick reply!
It may come from KOReader
Just noticed that when I disconnect from the KOReader side, Calibre unfreezes itself
ryt is offline   Reply With Quote
Old 03-18-2017, 12:41 PM   #5
ryt
Junior Member
ryt began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Mar 2017
Device: Kobo Aura One
In case this may help:

Spoiler:

Traceback (most recent call last):
File "site-packages/calibre/devices/smart_device_app/driver.py", line 615, in _call_client
File "site-packages/calibre/devices/smart_device_app/driver.py", line 657, in _receive_from_client
ControlError: Device responded with incorrect information
Error while trying to open <calibre.devices.smart_device_app.driver.SMART_DEV ICE_APP object at 0x115aefdd0> (Driver: <calibre.devices.smart_device_app.driver.SMART_DEV ICE_APP object at 0x115aefdd0>)
Traceback (most recent call last):
File "site-packages/calibre/gui2/device.py", line 296, in detect_device
File "site-packages/calibre/devices/smart_device_app/driver.py", line 51, in _synchronizer
File "site-packages/calibre/devices/smart_device_app/driver.py", line 1026, in open
File "site-packages/calibre/devices/smart_device_app/driver.py", line 51, in _synchronizer
File "site-packages/calibre/devices/smart_device_app/driver.py", line 615, in _call_client
File "site-packages/calibre/devices/smart_device_app/driver.py", line 657, in _receive_from_client
ControlError: Device responded with incorrect information
2017-03-18 16:51:05.265 Calibre[1955:33215] deliverNotificationWithTitle()
* Notification delivered.


Would there be a way to prevent this freeze in calibre even if the device responds with incorrect information?
ryt is offline   Reply With Quote
Advert
Old 03-18-2017, 01:28 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,373
Karma: 8012652
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by ryt View Post
Would there be a way to prevent this freeze in calibre even if the device responds with incorrect information?
The wireless device driver disconnects when the device responds in some inappropriate or unexpected fashion. In fact, that is the normal way a device disconnects.

If koreader thinks that it is connected but calibre does not then koreader is not following the protocol. The koreader people need to look at this and provide specific information if there is some problem in the driver. Apologies, but I don't have much interest in debugging someone else's app.
chaley is offline   Reply With Quote
Reply

« Previous Thread | Next Thread »

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Calibre connection only works using wifi (?) roadstar Calibre 1 12-28-2012 10:20 AM
Kindle Touch: execute script when wifi connection is established atordo Kindle Developer's Corner 5 07-13-2012 05:06 AM
Touch kobo freezes when deleting wifi networks wes101 Kobo Reader 10 11-10-2011 05:30 PM
Classic Unrooting my Nook Wifi lost Wifi connection: unable to save the hotspot SnerdlyBosco Nook Developer's Corner 2 03-08-2011 08:17 AM
PRS-950 Freezes and dropped WiFi connection valtchov Sony Reader 7 01-27-2011 06:41 PM


All times are GMT -4. The time now is 01:34 PM.

Contact Us - FAQ - Guidelines - Privacy - Top

MobileRead.com is a privately owned, operated and funded community.