Description of problem: From inside KMail, I got a signed GPG mail. From its header, I clicked on the hex GPG signature, which usually launches Kleopatra, but got the SIGTRAP instead. Version-Release number of selected component: kdepim-4.12.95-1.fc21 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/kleopatra -parent-windowid 65012367 -query 7A25556236BAA3A3 crash_function: g_wakeup_new executable: /usr/bin/kleopatra kernel: 3.14.0-0.rc8.git1.2.fc21.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #2 g_wakeup_new at /lib/libglib-2.0.so.0 #3 g_main_context_new at /lib/libglib-2.0.so.0 #4 QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate(_GMainContext*) at /lib/libQtCore.so.4 #5 QEventDispatcherGlib::QEventDispatcherGlib(QObject*) at /lib/libQtCore.so.4 #6 QThreadPrivate::createEventDispatcher(QThreadData*) at /lib/libQtCore.so.4 #7 QThreadPrivate::start(void*) at /lib/libQtCore.so.4
Created attachment 881098 [details] File: backtrace
Created attachment 881099 [details] File: cgroup
Created attachment 881100 [details] File: core_backtrace
Created attachment 881101 [details] File: dso_list
Created attachment 881102 [details] File: environ
Created attachment 881103 [details] File: limits
Created attachment 881104 [details] File: maps
Created attachment 881105 [details] File: open_fds
Created attachment 881106 [details] File: proc_pid_status
Created attachment 881107 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.