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.