From the other bug the only issue I see is that bug-buddy incorrectly handles
the "subject" field - in your ps output it looks like bug-buddy has exited, and
galeon is still stuck somehow, maybe due to NFS or something.

The fast scroll in bug-buddy is its attempt to use gdb to get info on the galeon
process, the error messages are because the galeon process is already toast.

Bug-buddy seems to be terminally confused by a crashing application and this
is when it is supposed to come into a play.  When I tried to type something
there bug-buddy at least was displaying a window and was acceptin keystrokes,
although apparently not a resulting string, so in this sense it appeared to
be running.

Yes, indeed, the whole situation was a mess.  This is why I was trying to
see how much help I can get from a bug-buddy.  I am afraid that it just added
to the general confusion. :-)

Pieces of 'ps' output were indeed captured after I gave up on bug-buddy.

OK, I'm just not clear on what exactly the bug-buddy bug is, so I'm closing this.
If the bug is enhancement-level it should probably go to
http://bugzilla.gnome.org anyhow.

Closing at hp's request.