tried with the LD_LIBRARY_LATH before the -p parameter, but it gave the same result.
Isn't the empty "" parameter after the -p the parameter of the -p parameter, i.e. an empty sudo prompt?
Yeah I figured that out shortly after posting, hence the edit. :-)
Here is the additional info you requested:
Booted, and then immediately executed the PND.
Mounted my volume.
entered the volume password:
Then I am asked for the administrator password:
I enter my user password.... OH, can this be the problem? Do I need to add truecrypt to a sudoers file or something, so this can work? Do we have an actual administrator password on the Pandora at all? But normally, when using sudo, I can enter my normal user password, and have admin rights.
I very much doubt it. As I understand it, entering your user password is exactly correct. Your user account is already given permission to use sudo, so there is no need for additional permission for truecrypt specifically.
I enter the user password, and this gives me this:
To be honest... I think it's misreporting the error.
The fact that it was reporting the library failure to begin with tells me that it was succeeding at obtaining administrator privileges all along, but the program is assuming a privileges problem if it doesn't see the expected outcome for any reason.
The fact that the dialogue box is otherwise empty tells me that nothing is now being sent to stderr by the process being executed, which in turn suggests to me that the command is being executed correctly, but it isn't doing something that the program expects it to do.
I think It would be useful at this point to add code similar to what M-HT suggested to discover the text of the command line being executed. Once we know what it was trying to execute, we should then be able to trace where it is being called from and what the testing conditions are, and hopefully, what the actual effect of the command is.
Is it possible that it worked and reported the error anyway? Maybe there is a race condition and the execution of the command took longer than the program was expecting, so it reported failure? I'd suggest you try it again then type mount in a terminal, to see if the volume was in fact mounted.