View Single Post
Old 07-23-2015, 01:49 AM   #189
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
In order to use such an option, one would have to select to do so, yes? Unless you suggest this be the default for everyone???

The solution is simple. calibre comes with a debug option. Use it ahead of time.


I use linux, and have never seen this problem, but as a general rule I always start in debug mode. I've proxied it, using the following bash script:

Code:
[eschwartz@arch ~]$ cat ~/bin/calibre
#!/bin/bash

if [ $# -eq 0 ] || [[ "$1" = "--detach" ]]; then
    echo -e "\n\n\nStarting calibre at $(date).\n\n\n" >> /tmp/calibre-debug-$USER.log 2>&1
    calibre-debug -g 2>&1 | tee -a /tmp/calibre-debug-$USER.log 
else
    /usr/bin/calibre $@
fi

Note: Only certain types of errors will appear, and the ones we might be looking for are vanishingly unlikely to be ammong them. Far more useful would be attaching a *proper* debugger to calibre, which might give better insight into how it interacts with other software/the Windows environment.



...
Hmm, seems you already suggested this. see post #124.

Last edited by eschwartz; 07-23-2015 at 03:07 AM.
eschwartz is offline   Reply With Quote