I followed these instructions - How to enable debugging | Joplin

Full console history here - joplinconsole.txt (41.1 KB)

Possibly relevant finding -

plugin markdown-prettier follows this 3 step load pattern -
step 1
/tmp/.mount_JoplincMcIPY/resources/app.asar/node_modules/@joplin/utils/dist/Logger.js:270 17:03:52: PluginService: Loading plugin from /home/blackfrank/.config/joplin-desktop/cache/shufo.markdown-prettier
step 2
/tmp/.mount_JoplincMcIPY/resources/app.asar/node_modules/@joplin/utils/dist/Logger.js:270 17:03:53: joplin.plugins: Starting plugin: shufo.markdown-prettier
step 3
/tmp/.mount_JoplincMcIPY/resources/app.asar/node_modules/@joplin/utils/dist/Logger.js:270 17:03:53: joplin.plugins: Finished running onStart handler: shufo.markdown-prettier (Took 226ms)

but for plugin joplin-batch I only see this 1 step load pattern -
step 1
/tmp/.mount_JoplincMcIPY/resources/app.asar/node_modules/@joplin/utils/dist/Logger.js:270 17:03:52: PluginService: Loading plugin from /home/blackfrank/.config/joplin-desktop/cache/rxliuli.joplin-batch

Should there be a step 2 and maybe step 3 as with markdown-prettier?

Nothing useful in log.txt