Hi Nolan,
I didn't notice serious leak in at-spi-registryd. I will take a look at
it these days.
Nolan Darilek wrote:
I tried checking out the latest at-spi-registryd from subversion. I
use stow to keep all locally-installed stuff separate and removable
from distribution-installed packages. I have
/usr/local/libexec/at-spi/at-spi-registryd, but
/usr/lib/at-spi/at-spi-registryd is still being started. How can I
start my own locally installed at-spi-registryd without replacing the
Ubuntu packaged version?
You need to build gnome-session to start the right at-spi-registryd. But
this is harder than just replace the system at-spi-registryd.
Until I figure this out, is there some way of stopping/restarting
at-spi-registryd mid-session? I tried killing it, but after that point
I was unable to get to a prompt where I could start a new instance.
Generally I can tell that I'm at a terminal or in the run dialog
because backspace on an empty line emits a beep, but nothing I did
brought me to this point.
After you kill at-spi-registryd, the GUI event can not be passed to ATs,
so it shouldn't be killed mid-session.
Regards,
Li
_______________________________________________
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
