Comment 4 for bug 357187

Thanks! It's my first bug to report where I knew where to report upstream.
I'll keep that in mind for the future!

BK

On Tue, Apr 7, 2009 at 2:23 PM, Andreas Moog <<email address hidden>
> wrote:

> Thanks for opening the upstream-report, this issue is confirmed. BTW:
> Usually it's not needed to open a bug on launchpad if there is one
> already upstream, we simply don't have the manpower (and womanpower. hi
> maco! ;-) ) to fix this ourselfs and rely on the upstream-work anyway.
>
> ** Bug watch added: GNOME Bug Tracker #578277
> http://bugzilla.gnome.org/show_bug.cgi?id=578277
>
> ** Also affects: seahorse via
> http://bugzilla.gnome.org/show_bug.cgi?id=578277
> Importance: Unknown
> Status: Unknown
>
> ** Changed in: seahorse (Ubuntu)
> Status: Incomplete => Triaged
>
> --
> Revoked subkeys not appearing as revoked
> https://bugs.launchpad.net/bugs/357187
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Seahorse: Unknown
> Status in “seahorse” source package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: seahorse
>
> v. 2.26.0
>
> As seen with a private/public personal key:
>
> Two revoked subkeys that appeared as revoked in previous version (as seen
> in Ubuntu 8.10) now appear without the revoked strikethrough. In the
> properties menu, there is no indication that the subkey revoked.
>
> Attempted to refresh with keyserver verified as having subkeys revoked
> failed to correct problem. Attempted to delete/import the key new from file
> with verified revoked signature, failed to correct problem.
>
> Cross-posted to http://bugzilla.gnome.org/show_bug.cgi?id=578277
>