Should current behavior of 'starting with no arguments' be preserved? or should we add a --generate or --doit or similar ?

If keyboxd sometimes takes 6 seconds, then I'm not surprised that stuff times out after 8 seconds occasionally. Or well. we need more numbers to determine that.

@ikloecker is https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=f23cef6f66a44c5c1cc8717f74b658d14fde04e5 needed to be forward ported to split gpgmepp ?

The only time I succeded in reproducing this was when I broke my gnupg setup and got a mix between gpg from one version and gpg-agent from another.

tested @ikloecker's patch succesful on amdahl.

I did a local change (on amdahl.d.o) changing _gpgme_subkey.expires to long long (ABI-break) and all tests succeeded.

It looks like the entirety of gpgme timestamping was missed when the 64bit time transition happened in Debian and Ubuntu.

Something went wrong during signing - the question is what.

I'm not sure I like the coming and going of the status bar.

I think there is a few things to consider.

Can we chop this in two (the KPasswordLineEdit thing and the rest) ? I think the rest can go in straight away, but I'd like to play around a bit with KPLE myself.

File dialogs
Code does use the standard Qt File dialog, but I_think I should redo it to use the static methods instead because that let the backend take over.

First start wizard