gpg crashed with SIGABRT in g10_log_bug()

[eric brinsfield]

gpg crashes everytime it tries to load up.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnupg 1.4.20-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
Uname: Linux 4.4.0-7-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 24 14:15:29 2016
ExecutablePath: /usr/bin/gpg
InstallationDate: Installed on 2015-12-04 (82 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151203)
ProcCmdline: gpg --status-fd 2 --no-tty --homedir /tmp/tmpwb2ejbmp --version
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnupg
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x404a20, argc=7, argv=0x7ffd22b28d68, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd22b28d58) at libc-start.c:289
 ?? ()
Title: gpg crashed with SIGABRT in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 g10_log_bug ()
 g10_log_bug0 ()
 main ()

[Tyler Hicks (tyhicks)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.