- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 29 2016
Note to self.
The problem is that editinteractor in edit_interactor_callback_impl checks
status_to_error before the GpgSignKeyEditInteractor::nextState implementation
has the chance to ignore that status with needsNoResponse.
A fix in GpgMEpp could be to ignore the error if the state machine was not
started. E.g. we have not yet send any command.
Attached patch fixes the problem. But I'm not sure that this does not cause
regressions e.g. when trying to add a uid to an expired key or trying to
actually sign expired uid's. :-/
Jun 8 2015
1.5.5 has been released. Closing.
Jun 5 2015
Oops. Long standing bug.
Fix in commit
0d28a696163677d6b34a802b6beddecd805d0fc7
Dec 11 2014
Fix has been released.
May 21 2014
Should be fixed with the current stable GnuPG and GPGME versions.
Apr 15 2014
Fixed with commit 2bb2618 for master. Will go into 1.5.0.
Thanks.
Apr 9 2014
May 28 2013
Duplicate of T1493
Please see T1493 - it is very likely the same reasons. I am not abale to
replicate it, though. The workaround is to configure gpgme with
--disable-fd-passing