Dear Maintainer,

What led up to the situation?
=============================

  Trying to add a sub-key to my private GPG key via the "Gnome keys"
  (a.k.a. seahorse) GUI.


What exactly did you do (or not do) that was effective (or ineffective)?
========================================================================

  1. Open "Passwords and Keys" (seahorse) via Gnome shell
  2. Select GnuPG keys in the sidebar
  3. Select my "Personal PGP key" in the list of keys
  4. Right-click on the selected key entry
  5. Select "Properties" in the context menu.
  6. Select the "Details" tab
  7. Click on "Add" in the "Subkeys" area
  8. Click on "OK" in the appearing "Add subkey to ..." dialog. The
     outcome appears to be the same independent of key type, key length,
     or expiration date (including "Never Expires").


What was the outcome of this action?
====================================

  A message window appears with the message
  ,----
  | Couldn't add subkey
  | General error
  `----
  and a "Close" button. Upon closing the window, the application
  continues to operate without perceivable issues.


What outcome did you expect instead?
====================================

  A new subkey to appear in the list of Subkeys.

Hi

I have the same issues and I believe this is related to the new
"KEYCONSIDERED" status in "recent" gpgme versions.

There's an upstream bug report here:
https://bugzilla.gnome.org/show_bug.cgi?id=778607 with a patch
attached that fixe  the issues for me.

Best,
--
Beren Minor

The same bug happens when I:

- check the checkbox "I trust signatures from 'USER' on others key"
- change the value of the field "You Trust The Owner:"
- "Sign This Key" (whatever option I choose)

The upstream patch
https://git.gnome.org/browse/seahorse/patch/?id=cdfc5b297d7420e47b9c973e8b8cb1b0fb576421
applies on 3.20.0.

The attached debdiff fixes the issue for me.

Hi!

Kjö Hansi Glaz:

Thanks! I'll look into it and will propose a NMU as this badly affects
Tails upcoming 3.0 (Stretch-based) release.

Now, I'm a little bit confused: the upstream bug + patch are about
something triggered by gpgme 1.7+, but this Debian bug was initially
reported against the version of Seahorse that's in Jessie, and Jessie
has gpgme 1.5.1. So I'm wondering 1. if they really are the same
problem; and 2. whether it's a regression in Stretch (if it is, then
it clearly needs to be fixed IMO, and then a freeze exception will be
more obviously needed).

So, Kjö, Beren and Sebastian: can one of you please confirm whether
you've experienced one of the problems this bug report is about on
Debian Jessie? If yes, what version of libgpgme11 do you
have installed?

Cheers,

0. "Add subkey to ..."
   * 8.2: General Error
   * stretch: General Error
   * stretch + patch: General Error

1. check the checkbox "I trust signatures from 'USER' on others key"
   * 8.2: OK
   * stretch: General Error
   * stretch + patch: OK

2. change the value of the field "You Trust The Owner:"
   * 8.2: OK
   * stretch: General Error
   * stretch + patch: OK

3. "Sign This Key" (whatever option I choose)
   * 8.2: General Error
   * stretch: General Error
   * stretch + patch: General Error

So you're right, the patch pointed on message #10 does not solve the
issue this bug was initially about, nor the error while signing key.
However, the patch solves the regressions introduced by Debian Stretch.

Debian 8.2 I have libgpgme11 1.5.1-6.

I'm trying to find if upstream has patches that solves the subkey and
signing issues.

This last line is wrong:

3. "Sign This Key" (whatever option I choose)
   * stretch + patch: OK

According to more tests, I *can* sign keys with the patch under sid and
stretch, while I can't without.

However, even without the patch, I can't add subkeys.

Hi dear Seahorse maintainers,

Kjö Hansi Glaz:

This regression badly affects Tails upcoming 3.0 (Stretch-based)
release. It doesn't break *all* Seahorse use cases, so arguably it's
not RC, but it breaks enough important features to warrant being fixed
in Stretch IMO.

So I'd like to do an NMU that cherry-picks the minimal fix that
upstream has already applied (and I'll request an unblock to the
release team). Is it OK with you, or do you prefer to handle
it differently?

If I don't hear from you in the next few days, I'll upload to
DELAYED/10.

Cheers,

intrigeri:

Sorry for the noise! This was meant for #859336, forget it.

Greetings.

I'm writing to you because I have a humanitarian request that I believe
could be incredibly impactful. I'm reaching out about the recent
devastating storm that tragically claimed many lives and affected numerous
individuals in Libya, including one of my clients. I would like to discuss
a proposal with you that could enable us to extend a helping hand to these
victims.

Looking forward to discussing this further with you.

Warm regards,
Mrs. Nathalie Herolds