Author: Gregory Nowak Date: To: Mark Hindley CC: Daniel Abrecht, dng, Dr. Nikolaus Klepp Subject: Re: [DNG] couldn't register with accessibility bus in Beowulf
On Wed, Mar 25, 2020 at 08:18:12AM +0100, Dr. Nikolaus Klepp wrote: > Stupid question: are you sure this is the showstopper? I have the same error message, but everything works as normal.
I am very, very sure this is the show stopper. Are you using orca, or
looking at your monitor?
On Wed, Mar 25, 2020 at 08:06:22AM +0000, Daniel Abrecht via Dng wrote: > To me, it seams to be caused by a combination of something `lightdm` does,
> and something `at-spi-bus-launcher` does not do.
> After a login with `lightdm`, the X11 root window has the `AT_SPI_BUS`
> property set (`xprop -root AT_SPI_BUS`), however, it seams the
> `at-spi-bus-launcher`/`at-spi2-registryd` instance which created that
> property does not exist anymore, causing applications to fail to connect to
> it. In addition to this, the presence of that property prevents a new
> instance of `at-spi-bus-launcher`
> from starting.
Thanks, that explanation does make sense.
On Wed, Mar 25, 2020 at 10:06:57AM +0000, Mark Hindley wrote: > I can conform that slim seems to do the right thing at the AT_SPI_BUS is set and
That makes sense, since slim doesn't have ATSPI support as far as I
know, where as lightdm does through lightdm-gtk-greeter.
> That bug also suggests another workaround of setting 'xserver-share=false' in
> /etc/lightdm/lightdm.conf which also seems to work.
OK, I'll explore that along with the other solution you mentioned.
On Wed, Mar 25, 2020 at 10:51:18AM +0000, Mark Hindley wrote: > There are also the most recent comments in Debian bug #911362 which relates
> to Buster and lightdm.
> Does installing libatk-adaptor help?
I'll report back on this too when I have access to the machine I did
the install on in a few hours. Thanks everyone.