Version-Release number of selected component: GConf2-3.2.6-6.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/gconfd-2 crash_function: g_wakeup_signal executable: /usr/libexec/gconfd-2 kernel: 3.9.9-301.fc19.i686 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_wakeup_signal at gwakeup.c:235 #1 g_main_loop_quit at gmain.c:3922 #2 gconfd_main_quit at gconfd.c:1142 #4 __bswap_32 at ../sysdeps/x86/bits/byteswap.h:47 #5 _nl_find_msg at dcigettext.c:781 #6 __dcigettext at dcigettext.c:639 #7 __dcgettext at dcgettext.c:52 #8 g_dgettext at ggettext.c:402 #9 x_shutdown at markup-backend.c:163 #10 gconf_backend_unref at gconf-backend.c:422 Potential duplicate: bug 957219
Created attachment 776648 [details] File: backtrace
Created attachment 776649 [details] File: cgroup
Created attachment 776650 [details] File: core_backtrace
Created attachment 776651 [details] File: dso_list
Created attachment 776653 [details] File: environ
Created attachment 776654 [details] File: limits
Created attachment 776655 [details] File: maps
Created attachment 776656 [details] File: open_fds
Created attachment 776657 [details] File: proc_pid_status
Created attachment 776658 [details] File: var_log_messages
I'm not sure, maybe by recovering from suspend mode..? reporter: libreport-2.1.8 backtrace_rating: 4 cmdline: /usr/libexec/gconfd-2 crash_function: g_wakeup_signal executable: /usr/libexec/gconfd-2 kernel: 3.11.4-201.fc19.i686.PAE package: GConf2-3.2.6-6.fc19 reason: Process /usr/libexec/gconfd-2 was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 500
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.