Re: Bad hang in gtkfilechooser after running beagle for awhile

["Sandy Armstrong" <sanfordarmstrong gmail com>]

On Tue, Mar 11, 2008 at 11:41 AM, D Bera <dbera web gmail com> wrote:
> >  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
>  >
>
> >  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?
>
>  If you can reproduce this, can you check two things:

Okay...several hours later, plus one restart of X (unrelated to this bug)...

>  - only one beagled and beagled-helper are running (ps ux | grep beagle)

Here's the output of ps ux | grep beagle:

sandy     1773  0.0  0.6  89768 28164 ?        SNl  06:51   0:01
beagled /usr/lib/beagle/BeagleDaemon.exe --replace --bg
sandy     1908  0.0  0.4  61648 18092 ?        SNl  Mar11   0:02
beagled-helper /usr/lib/beagle/IndexHelper.exe
sandy     6135  0.0  0.4  60860 18396 ?        SNl  Mar11   0:02
beagled-helper /usr/lib/beagle/IndexHelper.exe
sandy     7084  1.0  1.3 131428 55224 ?        SNl  Mar11  13:48
beagled /usr/lib/beagle/BeagleDaemon.exe --bg
sandy    10197  0.0  0.4  61772 18372 ?        SNl  00:55   0:02
beagled-helper /usr/lib/beagle/IndexHelper.exe
sandy    23138  0.0  0.0   3040   728 pts/4    R+   10:08   0:00 grep beagle
sandy    30328  0.0  0.4  61896 18600 ?        SNl  Mar11   0:02
beagled-helper /usr/lib/beagle/IndexHelper.exe
sandy    32666  0.0  0.4  63292 18708 ?        SNl  06:31   0:01
beagled-helper /usr/lib/beagle/IndexHelper.exe

>  - "beagle-info --status" does not hang

It certainly does hang.

>  If the first is yes, then it is a bug. Most likely libbeagle is not
>  able to connect to beagled. If the second is also yes, then probably
>  beagled is hanged for some reason. In that case
>  ~/.beagle/current-Beagle might have something to say.

Are you still interested in seeing ~/.beagle/current*?  I've copied
them over, just in case.  Now I'm going to restart beagle.

Sandy