[lrpirlet]

Hi Kovidgoyal.

Thanks for the suggestion... I will start by uncommenting all the print() and log.info() leftover in the kobo book plugin. I am sure that will (start to) show the path taken by the code... Then I may force a crash with sys.exit() in an attempt to show the stack...

However, I just wanted to report that I could access (for a short time) a laptop running calibre (5.??) under Ubuntu... and NO python installed beside calibre (at least synaptic did not show it as installed)

It seems that the behavior of the rpdb is not much better... Granted, it connected first time without any hiccup but once connected, the only reaction was an echo of the character I typed (h for help then l for list)... when I aborted in Calibre, the terminal displayed the result of ls... (Seems that the l character was still in the terminal buffer and was passed to the shell; l is an alias of ls in Ubuntu...)

Something may be wrong with the debugger (?? maybe only under python 3.8 ??)... I am not quite sure nor do I want to follow the debugger path, but I think it may be worse reporting.

Again, thanks for your help and that beautiful piece of software.