Version-Release number of selected component: dconf-0.15.2-2.fc19 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/dconf-service crash_function: dconf_writer_real_end executable: /usr/libexec/dconf-service kernel: 3.7.0-6.fc19.i686 remote_result: NOTFOUND uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 dconf_writer_real_end at dconf-writer.c:162 #1 dconf_writer_end at dconf-writer.c:207 #2 dconf_writer_handle_change at dconf-writer.c:281 #3 ffi_call_SYSV at ../src/x86/sysv.S:64 #4 ffi_call at ../src/x86/ffi.c:303 #5 g_cclosure_marshal_generic at gclosure.c:1454 #6 g_type_iface_meta_marshal at gclosure.c:1021 #9 g_signal_emitv at gsignal.c:3056 #10 _dconf_dbus_writer_skeleton_handle_method_call at dconf-generated.c:1091 #11 call_in_idle_cb at gdbusconnection.c:4737
Created attachment 673642 [details] File: backtrace
Created attachment 673643 [details] File: cgroup
Created attachment 673644 [details] File: core_backtrace
Created attachment 673645 [details] File: dso_list
Created attachment 673646 [details] File: environ
Created attachment 673647 [details] File: limits
Created attachment 673648 [details] File: maps
Created attachment 673649 [details] File: open_fds
Created attachment 673650 [details] File: proc_pid_status
Created attachment 673651 [details] File: smolt_data
Created attachment 673652 [details] File: var_log_messages
sorry. it is a new install backtrace_rating: 4 Package: dconf-0.15.2-2.fc19 Architecture: x86_64 OS Release: Fedora release 19 (Rawhide)
Loggin in after completing Rawhide installation backtrace_rating: 4 Package: dconf-0.15.2-2.fc19 OS Release: Fedora release 19 (Rawhide)
https://retrace.fedoraproject.org/faf/problems/213028/ This bug seems pretty serious and basically stops one from being able to configure f19 gnome desktop in any way. I think it also stops ibus input from working under gnome.
I believe this has been fixed for quite a while now.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
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.