Hi,
below is a patch against the 2.0 cvs to fix two minor problems:
(1) sometimes system error messages (e.g. through gpgme) which may contain
non UTF-8 encoded national characters are passed to libbalsa_information.
To avoid pango errors, first sanitise them (file src/information-dialog.
c);
(2) when gpg updates the trust database, it is not available for any
crypto operations. While the update is really fast (< 1 second) for small
(~50 keys) key rings, users with huge key rings will see balsa stalling
for as long as several minutes. We now check if gpg is available before
starting any crypto operation and return a "try again later" error if not.
Note that this is not a bullet-proof check as the update process might be
launched by a background process (think of crond) in the few milliseconds
between the check and the real crypto operation (a classical race...), but
it should help in the vast majority of cases (files libbalsa/rfc3156.[hc],
src/balsa-message.c).
Any comments?
Cheers,
Albrecht.
P.S.: Jean-Luc, could you please check if this really solves your problem?
Thanks, Albrecht.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Albrecht Dreß - Johanna-Kirchner-Straße 13 - D-53123 Bonn (Germany)
Phone (+49) 228 6199571 - mailto:albrecht.dress@arcor.de
_________________________________________________________________________
balsa-rfc3156-patch-2004-02-22.gz