seahorse crashs with critical error while listing gpg keys

[benste]

benste@benste-vpc-sb1c5e:~$ seahorse
** Message: init gpgme version 1.2.0

(seahorse:5265): GLib-GObject-CRITICAL **: Property 'icon' on class 'SeahorsePkcs11Certificate' has type 'gchararray' which is different from the type 'GIcon', of the property on interface 'GcrCertificateIface'

(seahorse:5265): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `GSimpleAsyncResult'

(seahorse:5265): GLib-GIO-CRITICAL **: g_simple_async_result_get_op_res_gpointer: assertion `G_IS_SIMPLE_ASYNC_RESULT (simple)' failed
Segmentation fault
---------
the first one doesn't crash the system

---------
reproduce:
go to seahorse, change tab to own keys,
rightclick on a key gPG to open it's details,
window appears for a 2nd. than seahorse crashes
-------
sidenotes - my system doesn't have any SMART Errors, hence the segfault shouldn't be caused by the HDD

-------------
I tagged this bug as security as I don't know how much information from my keyring is discolsed - neither whether this error can be used for an intrusion.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: seahorse 3.2.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Thu Mar 22 15:10:53 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
SourcePackage: seahorse
UpgradeStatus: Upgraded to oneiric on 2011-10-19 (154 days ago)

[benste (benste)]

only occures with both of my own keys not with foreign keys.

seahorse-plugins was installed but auto removed during the upgrade procedure

[Jamie Strandboge (jdstrand)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.