Re: [DNG] couldn't register with accessibility bus in Beowulf (workaround)
Wed, 25 Mar 2020 10:06:57 + - Mark Hindley : > I can conform that slim seems to do the right thing at the AT_SPI_BUS is set > and available. > > On Wed, Mar 25, 2020 at 08:06:22AM +, Daniel Abrecht via Dng wrote: > > Hi > > > > I've had that problem as well. [...] > > > > 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. I had the same issue too after dist-upgrade from ASCII to Beowulf. > > My current workaround is to remove the `AT_SPI_BUS` property, and then start > > `at-spi-bus-launcher` again: > > ``` > > xprop -root -remove AT_SPI_BUS > > /usr/lib/at-spi2-core/at-spi-bus-launcher & I have added: ~~~ export NO_AT_BRIDGE=1 ~~~ in `/etc/environment` and also I have installed `at-spi2-core`. This seems to have blocked the alerts, but I don't know if it's a real solution or just a workaround that doesn't solve the underlying problem. > Daniel, I get the same results as you with lightdm and your workaround is good > too. Although I don't have to restart the at-spi-bus-launcher process > manually, it is started automatically once a process tries to use it. > The issue seems to be that lightdm starts its own AT_SPI_BUS which is then > killed on login. But the AT_SPI_BUS property isn't removed so that it can be > relaunched in the user's session. This is depsite Debian #760740 being marked > as fixed. Also I am using lightdm (+ MATE). > That bug also suggests another workaround of setting 'xserver-share=false' in > /etc/lightdm/lightdm.conf which also seems to work. Maybe I'm wrong, but it seems to me that it is similar to the `export NO_AT_BRIDGE=1` workaround. If so the 'xserver-share=false' setting in the lightdm configuration seems to me to be more appropriate. Regards -- al3xu5 Say NO to copyright, patents, trademarks and any industrial design restrictions. Public GPG/PGP key ID: 4096 bit RSA key F94CFE23 Fingerprint: 59C6 9DC7 CD4B CF2F A190 E3DE 69C5 977B F94C FE23 pgpidHzgyeK_Z.pgp Description: Firma digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] couldn't register with accessibility bus in Beowulf (workaround)
Anno domini 2020 Wed, 25 Mar 16:31:48 -0700 Gregory Nowak scripsit: > 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? Oh my, I read "ocra", not "orca", sorry ... > > On Wed, Mar 25, 2020 at 08:06:22AM +, 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 +, Mark Hindley wrote: > > I can conform that slim seems to do the right thing at the AT_SPI_BUS is > > set and > > available. > > 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 +, Mark Hindley wrote: > > There are also the most recent comments[1] 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. > > Greg > > -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] couldn't register with accessibility bus in Beowulf (workaround)
On Wed, Mar 25, 2020 at 10:51:18AM +, Mark Hindley wrote: > There are also the most recent comments[1] in Debian bug #911362 which relates > to Buster and lightdm. > > Does installing libatk-adaptor help? No, already installed. > That bug also suggests another workaround of setting 'xserver-share=false' in > /etc/lightdm/lightdm.conf which also seems to work. Yup, that fixed it for me, thank you! I now get orca talking once I've logged in through lightdm. I'll be updating bug 99, since I also figured out just now the solution to the other lightdm issue I described there Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] couldn't register with accessibility bus in Beowulf (workaround)
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 +, 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 +, Mark Hindley wrote: > I can conform that slim seems to do the right thing at the AT_SPI_BUS is set > and > available. 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 +, Mark Hindley wrote: > There are also the most recent comments[1] 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. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] couldn't register with accessibility bus in Beowulf (workaround)
There are also the most recent comments[1] in Debian bug #911362 which relates to Buster and lightdm. Does installing libatk-adaptor help? Mark [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911362#27 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] couldn't register with accessibility bus in Beowulf (workaround)
Daniel and Gregory, I have had a look at this. I can conform that slim seems to do the right thing at the AT_SPI_BUS is set and available. On Wed, Mar 25, 2020 at 08:06:22AM +, Daniel Abrecht via Dng wrote: > Hi > > I've had that problem as well. It also prevents the auto-show feature of the > `onboard` onscreen keyboard from working (which was annoying on my Librem 5 > Phone, where I need that feature). > > 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. > > My current workaround is to remove the `AT_SPI_BUS` property, and then start > `at-spi-bus-launcher` again: > ``` > xprop -root -remove AT_SPI_BUS > /usr/lib/at-spi2-core/at-spi-bus-launcher & > ``` Daniel, I get the same results as you with lightdm and your workaround is good too. Although I don't have to restart the at-spi-bus-launcher process manually, it is started automatically once a process tries to use it. The issue seems to be that lightdm starts its own AT_SPI_BUS which is then killed on login. But the AT_SPI_BUS property isn't removed so that it can be relaunched in the user's session. This is depsite Debian #760740 being marked as fixed. That bug also suggests another workaround of setting 'xserver-share=false' in /etc/lightdm/lightdm.conf which also seems to work. Mark ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] couldn't register with accessibility bus in Beowulf (workaround)
Hi I've had that problem as well. It also prevents the auto-show feature of the `onboard` onscreen keyboard from working (which was annoying on my Librem 5 Phone, where I need that feature). 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. My current workaround is to remove the `AT_SPI_BUS` property, and then start `at-spi-bus-launcher` again: ``` xprop -root -remove AT_SPI_BUS /usr/lib/at-spi2-core/at-spi-bus-launcher & ``` After that, the `onboard` auto-show feature works for me for newly started applications again (this may require `onboard` restart). At least for GTK Applications, that is, I still have the problem of that feature not working for some QT applications, such as the `kate` editor. I assume that should be the same for other things which use the accessibility bus as well. Regards, Daniel Abrecht ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] couldn't register with accessibility bus in Beowulf
Hi! Anno domini 2020 Tue, 24 Mar 21:39:08 -0700 Gregory Nowak scripsit: > Hi all. > > I'd like to start a dedicated thread on this issue. Most users are > simply annoyed by the message in the subject in their > $HOME/.xsession-errors file. However, since one of the services that > can't connect to the accessibility bus is gnome-orca (the gtk screen > reader software orca for short), this error isn't just annoying to me, > it's a show > stopper as far as using the GUI goes. Stupid question: are you sure this is the showstopper? I have the same error message, but everything works as normal. > > I've been exploring this, and have some questions for people with the > same issue, which will hopefully start us on the road to solving it: > > 1. Do you also see these errors if you stop the login manager, and run > startx by hand? I don't, and orca runs just fine. > > 2. What login manager are you using, lightdm, slim, something else? > I'm using lightdm. If this happens regardless of the login manager > used, then it would seem to be login manager agnostic. > > 3. Does anyone here happen to have an already installed debian system > you could test on to see if you have this error message? If no one > else can check it in debian, I'll put doing a debian install on my to > do list. If this also happens in debian, upstream is the source of the > problem. If these messages don't show up in a .xsession-errors on a > debian system, then this is Beowulf specific it would seem. > > That's all from me for now. > > Greg > > -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] couldn't register with accessibility bus in Beowulf
Hi all. I'd like to start a dedicated thread on this issue. Most users are simply annoyed by the message in the subject in their $HOME/.xsession-errors file. However, since one of the services that can't connect to the accessibility bus is gnome-orca (the gtk screen reader software orca for short), this error isn't just annoying to me, it's a show stopper as far as using the GUI goes. I've been exploring this, and have some questions for people with the same issue, which will hopefully start us on the road to solving it: 1. Do you also see these errors if you stop the login manager, and run startx by hand? I don't, and orca runs just fine. 2. What login manager are you using, lightdm, slim, something else? I'm using lightdm. If this happens regardless of the login manager used, then it would seem to be login manager agnostic. 3. Does anyone here happen to have an already installed debian system you could test on to see if you have this error message? If no one else can check it in debian, I'll put doing a debian install on my to do list. If this also happens in debian, upstream is the source of the problem. If these messages don't show up in a .xsession-errors on a debian system, then this is Beowulf specific it would seem. That's all from me for now. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
