Operating System: FreeBSD 11.3
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 11.3-RELEASE-p5
OS Type: 64-bit
Processors: 4 × ACPI CPU
Memory: 31.7 GiB of RAM
gpg2 --version
gpg (GnuPG) 2.2.19
libgcrypt 1.8.5
I have just done a fresh installation. When I run the following
command, it is apparent that something is not copacetic.
gpg2 --refresh-keys
gpg: enabled debug flags: memstat trust extprog
gpg: mpi too large (28876 bits)
gpg: read_block: read error: Invalid packet
gpg: keydb: handles=108 locks=107 parse=224 get=224
gpg: build=0 update=0 insert=0 delete=0
gpg: reset=0 found=224 not=1 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=4438 cached=3013 good=2965 bad=48
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks
I have no idea what is wrong or how to fix it. I do know that this is
not the way it ran on my old, and now gone, PC.
--
Jerry
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 11.3-RELEASE-p5
OS Type: 64-bit
Processors: 4 × ACPI CPU
Memory: 31.7 GiB of RAM
gpg2 --version
gpg (GnuPG) 2.2.19
libgcrypt 1.8.5
I have just done a fresh installation. When I run the following
command, it is apparent that something is not copacetic.
gpg2 --refresh-keys
gpg: enabled debug flags: memstat trust extprog
gpg: mpi too large (28876 bits)
gpg: read_block: read error: Invalid packet
gpg: keydb: handles=108 locks=107 parse=224 get=224
gpg: build=0 update=0 insert=0 delete=0
gpg: reset=0 found=224 not=1 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=4438 cached=3013 good=2965 bad=48
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks
I have no idea what is wrong or how to fix it. I do know that this is
not the way it ran on my old, and now gone, PC.
--
Jerry
