Comment 5 for bug 2019086

Ok, I think I understood it.

My landscape license was recently re-generated (prior one expired) -- it is an internal field engineering temporary license for customer installation, btw -- and the new one is not correctly formatted (first time I'm using this one).

It is missing a header inside the signature part.

Where it now reads:

===========================8<---------------------------------------
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEENTODksx68VxYHaPbcqZmZcXIjuYFAmTlPXQACgkQcqZmZcXI
===========================8<---------------------------------------

It should read something like:

===========================8<---------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (MingW32)

iQEzBAEBCgAdFiEENTODksx68VxYHaPbcqZmZcXIjuYFAmTlPXQACgkQcqZmZcXI
===========================8<---------------------------------------

(see the line with version and operating system). I added a random header (the one shown above) and now gpg works fine and I don't have the charm errors anymore.

@dparv, I suspect you are using that same file.