Version-Release number of selected component: gnupg-1.4.16-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gpg --charset utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2 --import crash_function: g10_log_bug executable: /usr/bin/gpg kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (10 frames) #2 g10_log_bug at logger.c:241 #3 g10_log_bug0 at logger.c:249 #4 merge_selfsigs at getkey.c:2322 #5 lookup at getkey.c:2764 #6 get_pubkey at getkey.c:371 #7 signature_check2 at sig-check.c:77 #8 signature_check at sig-check.c:53 #9 check_revocation_keys at sig-check.c:447 #10 merge_selfsigs_main at getkey.c:1803 #11 merge_selfsigs at getkey.c:2325
Created attachment 901053 [details] File: backtrace
Created attachment 901054 [details] File: cgroup
Created attachment 901055 [details] File: core_backtrace
Created attachment 901056 [details] File: dso_list
Created attachment 901057 [details] File: environ
Created attachment 901058 [details] File: limits
Created attachment 901059 [details] File: maps
Created attachment 901060 [details] File: open_fds
Created attachment 901061 [details] File: proc_pid_status
Created attachment 901062 [details] File: var_log_messages
Can you reproduce this outside enigmail? It looks like this bug alert is triggered when trying to self-sign a key and its type isn't PKT_PUBLIC_KEY or PKT_SECRET_KEY
I do not know how to reproduce this outside enigmail. Feel free to close this bug. I will reopen it if it happens again.