Version-Release number of selected component: gnomint-1.2.1-10.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: gnomint crash_function: tls_creation_data_free executable: /usr/bin/gnomint kernel: 3.13.10-200.fc20.i686 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #7 tls_creation_data_free at tls.c:1647 #8 ca_creation_thread at ca_creation.c:151 #9 g_thread_proxy at gthread.c:798 #10 g_deprecated_thread_proxy at deprecated/gthread-deprecated.c:310
Created attachment 888082 [details] File: backtrace
Created attachment 888083 [details] File: cgroup
Created attachment 888084 [details] File: core_backtrace
Created attachment 888085 [details] File: dso_list
Created attachment 888086 [details] File: environ
Created attachment 888087 [details] File: limits
Created attachment 888088 [details] File: maps
Created attachment 888089 [details] File: open_fds
Created attachment 888090 [details] File: proc_pid_status
Created attachment 888091 [details] File: var_log_messages
Another user experienced a similar problem: 1. Opened the application. 2. Created a new certificates database. 3. Started the process of creating a new CA. 4. After the step that asks for a URL where the CRL will be stored, the wizard and application crashed. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gnomint crash_function: tls_creation_data_free executable: /usr/bin/gnomint kernel: 3.17.8-200.fc20.x86_64 package: gnomint-1.2.1-10.fc20 reason: gnomint killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.