MobileRead Forums - View Single Post - When Calibre fails from a command line, it doesn't complain or set the RC

davidfor · 03-25-2021, 09:06 PM

Is the calibre that is run from the Task Scheduler running under the same user?

When I use "calibre-debug -s", and no calibre is running, I get:

Code:

C:\Users\davidfor>calibre-debug -s
Failed to contact running instance of calibre
Failed to connect to Listener at: \\.\pipe\CalibreGUI-davidforx with error: QLocalSocket::connectToServer: Invalid name

That has my username as part of the listener name. If the running calibre instance is in a different user, then the listener will be different and this won't find it.

And I don't consider the above to be an error. The message could be cleaner, but, that is a valid result when there is nothing to shutdown. If the listener was found and the shutdown didn't happen, that would be a different matter.

03-25-2021, 09:06 PM	#2
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Is the calibre that is run from the Task Scheduler running under the same user? When I use "calibre-debug -s", and no calibre is running, I get: Code: C:\Users\davidfor>calibre-debug -s Failed to contact running instance of calibre Failed to connect to Listener at: \\.\pipe\CalibreGUI-davidforx with error: QLocalSocket::connectToServer: Invalid name That has my username as part of the listener name. If the running calibre instance is in a different user, then the listener will be different and this won't find it. And I don't consider the above to be an error. The message could be cleaner, but, that is a valid result when there is nothing to shutdown. If the listener was found and the shutdown didn't happen, that would be a different matter.