Description of problem: Crash occurred at or before login. I had just recently yum updated a number of packages, including kernel etc. and checkdns, and this happened after the next reboot. Nonetheless, it seems to be working in my panel now. Version-Release number of selected component: dnssec-trigger-0.11-20.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/dnssec-trigger crash_function: exit executable: /usr/bin/dnssec-trigger-panel kernel: 3.13.5-202.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1024 Truncated backtrace: Thread no. 1 (2 frames) #13 exit at exit.c:104 #15 _start
Created attachment 872693 [details] File: backtrace
Created attachment 872694 [details] File: cgroup
Created attachment 872695 [details] File: core_backtrace
Created attachment 872696 [details] File: dso_list
Created attachment 872697 [details] File: environ
Created attachment 872698 [details] File: exploitable
Created attachment 872699 [details] File: limits
Created attachment 872700 [details] File: maps
Created attachment 872701 [details] File: open_fds
Created attachment 872702 [details] File: proc_pid_status
Created attachment 872703 [details] File: var_log_messages
The issue happens in the exit handler when glib tries to do all sorts of things. From what I heard, there's not much you can do safely in an exit handler. I also heard rumours that glib isn't careful about it. I can't tell whether it's a problem in glib itself or whether the panel does something that triggers an action on exit. I quickly skimmed the code and I don't see anything suspicious except extensive usage of threads. The retrace URL is no longer working, so I can't assess the occurence of this issue. It may well be a race condition intrinsic to the glib library that cannot be undone in dnssec-trigger.
https://retrace.fedoraproject.org/faf/reports/44491/
(In reply to Pavel Šimerda (pavlix) from comment #13) > https://retrace.fedoraproject.org/faf/reports/44491/ Ah, that one looks only similar, the backtrace doesn't include glib nor g_realloc.
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.