Red Hat Bugzilla – Bug 116404
Login fails and gconfd segfaults
Last modified: 2007-11-30 17:10:37 EST
I am running a laptop with Fedora core 1 on it. I used YUM to
upgrade yesterday and today it will not load my desktop. The xfree86
comes up to the login prompt (run level 5) I log in and when the
screen goes blank to load my personal settings it doesn't load
anything. If I use run level 3 and "statrx" from the console x-
window starts up but I only have a mouse X on the screen. If I ctrl-
alt-backspace to get into the console again, there are no errors?
Feb 20 11:09:27 qaneh gconfd (root-3614): received signal 11, dumping
core. Please report a GConf bug.
Can you attach gdb to the running gconfd and get a backtrace?
Just run gdb and type 'attach <pid>' where pid is the process id of
I'm on FC3T1 and getting a signal 11 from gconfd 20 minutes after
Firefox kicks it off (using KDE3). GConf2 version: 2.7.90-1. I
installed debug-info and attached gdb to it.
Should I start a new bugzilla entry for this?
This is the backtrace after it segfaults:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 1291)]
0x4014ed03 in g_node_max_height () from /usr/lib/libglib-2.0.so.0
#0 0x4014ed03 in g_node_max_height () from /usr/lib/libglib-2.0.so.0
#1 0x4014ed18 in g_node_max_height () from /usr/lib/libglib-2.0.so.0
#2 0x4014f175 in g_node_traverse () from /usr/lib/libglib-2.0.so.0
#3 0x40044773 in gconf_listeners_remove_if (listeners=0x80614f0,
predicate=0x3, user_data=0x3) at gconf-listeners.c:810
#4 0x0804bd2a in gconf_database_drop_dead_listeners (db=0x3)
#5 0x08051d7d in periodic_cleanup_timeout (data=0x0) at gconfd.c:1017
#6 0x40147078 in g_main_context_wakeup () from /usr/lib/libglib-2.0.so.0
#7 0x401444cb in g_main_context_dispatch () from
#8 0x40145f52 in g_main_context_acquire () from /usr/lib/libglib-2.0.so.0
#9 0x401461ff in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#10 0x08050baf in main (argc=2, argv=0x3) at gconfd.c:869
*** This bug has been marked as a duplicate of 130524 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.