Bad hang in gtkfilechooser after running beagle for awhile

"Sandy Armstrong" <[email protected]>
Newsgroups gmane.comp.gnome.dashboard.devel
Message-ID <[email protected]>
Hi folks,

I noticed that after being logged in for awhile with beagle running,
any time I try to bring up an open or save dialog in
gedit/firefox/whatever, that application hangs.  I managed to get this
stack trace from gedit:

(gdb) thread apply all bt

Thread 1 (Thread 0xb6c318d0 (LWP 5935)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6ed0e01 in connect () from /lib/libpthread.so.0
#2  0xb3eaa064 in beagle_util_daemon_is_running () from /usr/lib/libbeagle.so.0
#3  0xb779956d in _gtk_search_engine_beagle_new ()
    at gtksearchenginebeagle.c:395
#4  0xb7798cba in _gtk_search_engine_new () at gtksearchengine.c:119
#5  0xb7833a72 in gtk_file_chooser_default_constructor (type=138065688,
    n_construct_properties=1, construct_params=0x83b10a0)
    at gtkfilechooserdefault.c:276
#6  0xb6e8d748 in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#7  0xb6e8e2f5 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#8  0xb6e8e400 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#9  0xb7824088 in _gtk_file_chooser_default_new (file_system=0x0)
    at gtkfilechooserdefault.c:11149
#10 0xb7838cec in gtk_file_chooser_widget_constructor (type=137791912,
    n_construct_properties=1, construct_params=0x8372190)
    at gtkfilechooserwidget.c:103
#11 0xb6e8d748 in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#12 0xb6e8e290 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#13 0xb6e8e400 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#14 0xb78358a5 in gtk_file_chooser_dialog_constructor (type=137830512,
---Type <return> to continue, or q <return> to quit---
    n_construct_properties=3, construct_params=0x82a1f28)
    at gtkfilechooserdialog.c:281
#15 0xb6e8d748 in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#16 0xb6e8e2f5 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#17 0xb6e8e400 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#18 0x08078f6e in gedit_file_chooser_dialog_new ()
#19 0x0806cf02 in _gedit_cmd_file_open ()
#20 0xb6e95bcf in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#21 0xb6e88919 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#22 0xb6e9b9ed in ?? () from /usr/lib/libgobject-2.0.so.0
#23 0x08118580 in ?? ()
#24 0x00000000 in ?? ()


Checking in gnome-system-monitor I did notice both beagled and
beagled-helper running.  I killed both and was able to use open/save
dialogs again without hanging.

I'm on OpenSUSE 10.3, running Beagle 0.2.18, GNOME 2.20.0, and GTK+ 2.12.20.

Should I be doing further debugging to get a good bug report, or is
this a waste of time because of the old Beagle version?

Thanks,
Sandy
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.