On Fri, Sep 25, 2009 at 01:29:45PM +0200, Emilio Pozuelo Monfort wrote:

> I've just reproduced this with 2.26 and 2.28 while testing if the 2.28 update
> was fine. The reason (pointed out by Mario Lang) was that at-spi-registryd
> wasn't running (it should be if you have a11y enabled). Is it running for you
> when hitting this bug? If you launch it (I did it by going to
> gnome-at-properties and disabling and enabling "Enable a11y technology"), does
> it work? The buttons should then work, and the keyboard itself is in compose.

Ah, manually starting at-spi-registryd makes GOK work. But according to the
Assistive Technologies configuration panel, it was enabled...

Anyway, now that I see GOK in action I know that this is not what I expected of
an "onscreen keyboard", so I guess I will not use it. But if you want me to
test anything to see why it fails to run as it should, please ask.

-- 
Met vriendelijke groet / with kind regards,
      Guus Sliepen <g...@debian.org>

Attachment: signature.asc
Description: Digital signature

Reply via email to