Ok - the error is not in gcrypt/pk-crypto.scm. Line 114 in the function string->canonical-sexp is where the error is thrown when an invalid sexp is passed to the function. In my case, the error was in a sub file in my configuration detailing the authorisation key - I had missed not one, but two brackets at the end of the file!