Bug 426436 - Kleopatra: Error message while refreshing OpenGPG keys
Summary: Kleopatra: Error message while refreshing OpenGPG keys
Status: RESOLVED NOT A BUG
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 3.1.11
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-12 10:25 UTC by Gerard Seibert
Modified: 2020-09-12 16:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Kleopatra log file (194.29 KB, text/plain)
2020-09-12 10:25 UTC, Gerard Seibert
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gerard Seibert 2020-09-12 10:25:47 UTC
Created attachment 131572 [details]
Kleopatra log file

SUMMARY


STEPS TO REPRODUCE
1. <Tools>
2. <Refresh OpenPGP Signatures>
3. 

OBSERVED RESULT

Operation lends with an error message

EXPECTED RESULT

It would complete successfully.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

Kleopatra libraries:

KDE Frameworks 5.73.0
Qt 5.15.0 (built against 5.15.0)
The xcb windowing system

Operating System: FreeBSD 11.4
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 11.4-RELEASE-p3
OS Type: 64-bit
Memory: 31.7 GiB of RAM
Graphics Processor: GeForce GT 1030/PCIe/SSE2

ADDITIONAL INFORMATION

I have attached a copy of the log file. I am not even sure if this is really a bug or just a harmless message. The log starts with:

An error occurred while trying to refresh OpenPGP certificates.
The output from /usr/local/bin/gpg2 was:
gpg: enabled debug flags: memstat
gpg: refreshing 190 keys from hkp://pool.sks-keyservers.net

//truncated//

and ends with this:

gpg: Total number processed: 151
gpg:              unchanged: 151
gpg: keydb: handles=303 locks=151 parse=492 get=492
gpg:        build=0 update=0 insert=0 delete=0
gpg:        reset=0 found=492 not=1 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=7595 cached=5482 good=5434 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
Comment 1 Andre Heinecke 2020-09-12 13:47:35 UTC
Comment on attachment 131572 [details]
Kleopatra log file

Uhm,.. this should be deleted but I don't know how to delete log files here. It contains personal information data of others.
Comment 2 Andre Heinecke 2020-09-12 13:50:46 UTC
Hi,

you have enabled memstat debugging of GnuPG somehow. This reports memory debugging messages on stderror and Kleopatra thinks "Oh Stderror, let us report an error"

You can disable that in ~/.gnupg/gpg.conf   There is probably a line in there like "debug memory" or so.


All outpoot looks like it is working as expected to me.
Comment 3 Gerard Seibert 2020-09-12 16:19:10 UTC
(In reply to Andre Heinecke from comment #2)

You are probably right. I did remove any mention of "debug" in the gpg.conf file, but the same error message is displayed.

This is my gpg.conf file:

###+++--- GPGConf ---+++###
utf8-strings
auto-key-retrieve
debug-level none

###+++--- GPGConf ---+++### Sat Sep 12 12:03:37 2020 EDT
# GPGConf edited this configuration file.
# It will disable options before this marked block, but it will
# never change anything below these lines.

default-key  3873063887DEC564
use-agent
keyserver  hkp://pool.sks-keyservers.net
no-secmem-warning