Hi Athanasius, Athanasius wrote: >> If this does not succeed in producing debugging output: I'm running out >> of ideas for now... :-/ > > I'd hazard a guess it's more to do with one of the libraries, but have > no idea which of the many might be the root of the problem. Did this > newer version of gnucash start pulling in/using some library it didn't > before?
Yes, Gnucash 2.2.6 added support for AqBanking and hence additionally pulls in at least libaqbanking and libgwenhywfar. The message "Libgcrypt version mismatch" is for sure generated by libgwenhywfar. But I see no reason at all why the gcry_check_version() called by libgwenhywfar fails (we've checked versions earlier without a single suspicious evidence). Maybe a backtrace helps to enlighten the situation by displaying the actual values handed over to gcry_check_version().... Can you provide a backtrace by running Gnucash in gdb as described here? http://svn.gnucash.org/trac/browser/gnucash/tags/2.2.6/HACKING#L84 Once Gnucash crashed you need to type "bt" at the gdb prompt to get the actual backtrace. As a last resort and cheap workaround you can avoid the loading of the AqBanking module entirely by renaming the file libgncmod-aqbanking.so (in directory /usr/lib/gnucash/gnucash/) to something like libgncmod-aqbanking.so.broken. This way you might at least get Gnucash working again. To prevent future updates re-installing this file again I suggest to use dpkg-divert (as root) which makes this move known to Dpkg (future updates will then install this file to the renamed location): dpkg-divert --rename \ --divert /usr/lib/gnucash/gnucash/libgncmod-aqbanking.so.broken \ --add /usr/lib/gnucash/gnucash/libgncmod-aqbanking.so HTH Regards Micha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
