Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#50094 - [gnupg] gnugpg has been complied with the memstat debug flag
Attached to Project:
Arch Linux
Opened by Michael Van Delft (xotc) - Tuesday, 19 July 2016, 09:01 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 20 July 2016, 13:18 GMT
Opened by Michael Van Delft (xotc) - Tuesday, 19 July 2016, 09:01 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 20 July 2016, 13:18 GMT
|
DetailsDescription:
It looks like gnupg has been complied with the memstat debug flag, this causes a lot of messy an unnecessary output. Additional info: * package version: 2.1.14-1 Steps to reproduce: Running any gpg command from the terminal will result in a few lines of debug output. $ gpg --sign test-file.txt gpg: enabled debug flags: memstat gpg: random usage: poolsize=600 mixed=0 polls=0/3 added=15/528 outmix=0 getlvl1=0/0 getlvl2=0/0 gpg: secmem usage: 1344/32768 bytes in 2 blocks $ |
This task depends upon
It appears that it was my ~/.gnupg/gpg.conf file that had "debug-level basic" enabled. I'm not sure where it came from, this was on a fresh install and I'd never edited that file. I suspect it may have been one of the KDE tools (kgpg or kleopatra) I'll keep digging and see why that setting was there.