User Details
- User Since
- Mar 27 2017, 4:47 PM (404 w, 36 m)
- Availability
- Available
Jun 9 2024
I confirmed that this is present in version 2.2.40 on debian as well.
Sep 8 2021
I verified that manually putting the DB in WAL mode also resolved this issue, since writers don't block readers in WAL mode.
Oct 11 2019
I've also noticed this issue on windows when trying to symlink %APPDATA%\gnupg to $HOME/.gnupg under msys32.
Oct 30 2017
Sep 6 2017
Sep 5 2017
Sep 11 2015
yes, this was fixed in 2.1.8
Aug 14 2015
I also might add, I cleared out the %appdata%\gnupg directory before trying to
import the key. I also tried importing my public key first, then importing
the secret key, with the same result.
Jun 12 2015
I tried it in PuTTY without screen and it was not skewed. The line draw
characters looked funny (which I'm assuming is a Unicode thing), but they
were in a rectangle.
Jun 4 2015
OK, I'll try that too.
I will try this afternoon.
Jun 3 2015
On Tue, Jun 2, 2015, 11:19 PM Neal Walfield via BTS <gnupg@bugs.g10code.com>
wrote:
Here is my .screenrc
#change the hardstatus settings to give
an window list at the bottom of the
#screen, with the time and date and with
the current window highlighted
hardstatus alwayslastline
hardstatus string '%{= bK}%-Lw%{=
KW}%50>%n%f* %t%{= bK}%+Lw%< %{= kG}%-=%D
%d %M %Y %c:%s%{+b y} %H %l'
deflogin on
shell /usr/bin/bash
vbell on
I was using PuTTY 6.4 on Windows 7 64 bit.