[twobob]

Okay. One option that you could do is redirect the failure output to a visible file.

Inside the script that starts librerator (in this case) you could put a redirector for the error output.

I see that you have chosen NOT to start librerator using KUAL (and I dont use launchpad but) I am going to assume the principle is similar.

here is an example of redirecting program output using kual:

You put an extra &> /path/to/file-for-output.txt on the call

{"name": "Open last document", "priority": 2, "action": "/mnt/us/librerator/librerator.sh &> /mnt/us/documents/lib-fail.txt"}

you can also redirect ALL error out like 2>&1

{"name": "Open last document", "priority": 2, "action": "/mnt/us/librerator/librerator.sh 2>&1 /mnt/us/documents/lib-fail.txt"}

Here is an examples of that in action AND I JUST WOKE UP SO CHECK I GOT THIS RIGHT
http://www.cyberciti.biz/faq/redirec...err-to-stdout/

This will give you a human readable file to see what the program is complaining about.



Now... About S S I

I checked and HERE are the keys (in launchpad) for librerator

[Actions]
# start librerator with filebrowser in /mnt/us/documents
L L = !/mnt/us/librerator/librerator.sh /mnt/us/documents
# start librerator without framework in /mnt/us/documents
L K = !/mnt/us/librerator/librerator.sh --framework_stop /mnt/us/documents
# restart amazon framework - when it got irritated
L R = !/etc/init.d/framework restart

so one could possibly add to that like

# start librerator with filebrowser in /mnt/us/documents with some output
L Z = !/mnt/us/librerator/librerator.sh /mnt/us/documents 2>&1 /mnt/us/documents/lib-fail.txt

please check the launchpad documentation (or prior examples) to make sure I didn't get that wrong.

Anyways if all that fails...

install KUAL and check if you can run it via that.

You can always uninstall KUAL afterwards if you really don't wanna use it.
Hope it helps.