Quote:
Originally Posted by bambuko
That was most useful reply - thank you!
Yet again I have learned something (not a bad day then?  )
I will look at this shortcut business, although my main priority should be sorting out issues with Qt crashing on PC when running Calibre, causing segmentation faults (real PITA  )
I know Kovid told me  but it's not so easy when you trying to learn from scratch  |
I would just go with running gdb (GNU debugger):
Code:
$ gdb calibre
(gdb) run
(gdb) ### calibre errors out
(gdb) backtrace
(gdb) ### Bunch of debugging info
and then posting it for Kovid to look at, since he probably knows more about debugging calibre than we do.
Quote:
BTW when I mess around with BIN_DIR rather than falling back on system search and finding it for me (I know it exists) it simply tells me:
Code:
PROGRAM FILES: Using System search path
--------------------------------------------------
TEMPORARY FILES: /tmp/CALIBRE_TEMP
--------------------------------------------------
Press CTRL-C if you do not want to continue
Press ENTER to continue and start Calibre
Starting up Calibre from portable directory "/opt/calibre"
/opt/calibre/calibre-portable.sh: line 203: calibre: command not found
Script completed hit RETURN to close window.
|
Wouldn't that heavily imply that the search path (from within the script, but we haven't exactly changed it...) cannot find "calibre"?
If you change the last line from "$CALIBRE" to "calibre" you should get the same result??
Right before the last line, try inserting "command -v calibre; command -v $CALIBRE" -- they should both point to "/usr/bin/calibre" -- that shouldn't actually be any different than trying to launch calibre directly via the command line, though...
And I assume you have not installed the system calibre to /opt/calibre (default) then.