View Single Post
Old 09-17-2016, 10:59 AM   #4
ShellShock
Wizard
ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.
 
ShellShock's Avatar
 
Posts: 1,178
Karma: 2431850
Join Date: Sep 2008
Device: IPad Mini 2 Retina
I ran calibre-debug -g, and on closing Calibre got this in the log:

Code:
Started up in 2.17 seconds with 481 books
C:\Program Files\Calibre\pylib.zip\cherrypy\process\wspbus.py:225: RuntimeWarning: The main thread is exiting, but the Bus is in the states.STARTED state; shutting it down automatically now. You must either call bus.block() after start(), or call bus.exit() before the main thread exits.
I then uninstalled the iOSReaderApp and Marvin XD plugins, which I don't use anymore. That fixed the original problem but now I had a different problem - when I ran Calibre I got this:

Code:
calibre-debug -g
calibre 2.68 [64bit]  embedded-python: True is64bit: True
Windows-8-6.2.9200 Windows ('64bit', 'WindowsPE')
('Windows', '8', '6.2.9200')
Python 2.7.9
Windows: ('8', '6.2.9200', '', 'Multiprocessor Free')
Qt: Untested Windows version 10.0 detected!
Successfully initialized third party plugins: DeDRM (6, 5, 1) && Open With (1, 5, 9) && Modify ePub (1, 3, 13)
devicePixelRatio: 1.0
logicalDpi: 96.0 x 96.0
physicalDpi: 95.8113948919 x 95.9160839161
Starting up...
Started up in 2.01 seconds with 481 books
And when I closed Calibre, I saw the modal message:

Code:
Shutting down
Shutting down the content server. This could take a while...
Calibre then froze for about 110 seconds before terminating. All calibre processes were terminated at this point.

Then I remembered that last year I had enabled the content server, but I never really used it. So I went into preferences and turned off starting the content server automatically. Now Calibre closes normally - problem solved. I am not sure if the content server is meant to take that long to shut down though (if you want to use it, which I don't).
ShellShock is offline   Reply With Quote