Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #215275 > unrolled thread

at-spi-dbus-launcher not responding

Started byMike Kupfer <mkupfer@alum.berkeley.edu>
First post2019-10-20 00:50 +0200
Last post2019-10-22 10:10 +0200
Articles 6 — 5 participants

Back to article view | Back to linux.debian.user


Contents

  at-spi-dbus-launcher not responding Mike Kupfer <mkupfer@alum.berkeley.edu> - 2019-10-20 00:50 +0200
    Re: at-spi-dbus-launcher not responding Cindy Sue Causey <butterflybytes@gmail.com> - 2019-10-20 01:00 +0200
      Re: at-spi-dbus-launcher not responding Mark Allums <maa@allums.com> - 2019-10-20 10:00 +0200
        Re: at-spi-dbus-launcher not responding Mike Kupfer <mkupfer@alum.berkeley.edu> - 2019-10-21 00:10 +0200
          Re: at-spi-dbus-launcher not responding Jean-Philippe MENGUAL <jpmengual@debian.org> - 2019-10-22 00:30 +0200
            Re: at-spi-dbus-launcher not responding Curt <curty@free.fr> - 2019-10-22 10:10 +0200

#215275 — at-spi-dbus-launcher not responding

FromMike Kupfer <mkupfer@alum.berkeley.edu>
Date2019-10-20 00:50 +0200
Subjectat-spi-dbus-launcher not responding
Message-ID<yT5HP-4xb-1@gated-at.bofh.it>
I have a system running bullseye.  When I try to log out, or shut down,
from MATE, I invariably get a popup that tells me that
at-spi-dbus-launcher is not responding.  I click on "logout anyway", and
the system does eventually log me out, but there's a delay.

I tried disabling the AT-SPI daemon and the Orca screen reader in my
startup applications, but that hasn't helped.

Does anyone know what's going on here?

thanks,
mike

[toc] | [next] | [standalone]


#215276

FromCindy Sue Causey <butterflybytes@gmail.com>
Date2019-10-20 01:00 +0200
Message-ID<yT5Rv-4BE-1@gated-at.bofh.it>
In reply to#215275
On 10/19/19, Mike Kupfer <mkupfer@alum.berkeley.edu> wrote:
> I have a system running bullseye.  When I try to log out, or shut down,
> from MATE, I invariably get a popup that tells me that
> at-spi-dbus-launcher is not responding.  I click on "logout anyway", and
> the system does eventually log me out, but there's a delay.
>
> I tried disabling the AT-SPI daemon and the Orca screen reader in my
> startup applications, but that hasn't helped.
>
> Does anyone know what's going on here?


Hi, mike, I don't know, but, as soon as I read "Orca", I thought of
the Debian-Accessibility list:

https://lists.debian.org/debian-accessibility/

The "at-spi-dbus" in your post was familiar from my inbox, but there's
not much left in there about it. Ironically of sorts, I did find this
several year old bug where potentially similar delay activity was
happening during *login* instead of logout:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840618

Apologies if you already know about the Debian-Accessibility list. Good luck!

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

[toc] | [prev] | [next] | [standalone]


#215277

FromMark Allums <maa@allums.com>
Date2019-10-20 10:00 +0200
Message-ID<yTei6-1G8-1@gated-at.bofh.it>
In reply to#215276
On 10/19/2019 5:54 PM, Cindy Sue Causey wrote:
> On 10/19/19, Mike Kupfer <mkupfer@alum.berkeley.edu> wrote:
>> I have a system running bullseye.  When I try to log out, or shut down,
>> from MATE, I invariably get a popup that tells me that
>> at-spi-dbus-launcher is not responding.  I click on "logout anyway", and
>> the system does eventually log me out, but there's a delay.
>>
>> I tried disabling the AT-SPI daemon and the Orca screen reader in my
>> startup applications, but that hasn't helped.
>>
>> Does anyone know what's going on here?
>
> Hi, mike, I don't know, but, as soon as I read "Orca", I thought of
> the Debian-Accessibility list:
>
> https://lists.debian.org/debian-accessibility/
>
> The "at-spi-dbus" in your post was familiar from my inbox, but there's
> not much left in there about it. Ironically of sorts, I did find this
> several year old bug where potentially similar delay activity was
> happening during *login* instead of logout:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840618

I am not running Orca, but I have the same issue.

Mark

[toc] | [prev] | [next] | [standalone]


#215301

FromMike Kupfer <mkupfer@alum.berkeley.edu>
Date2019-10-21 00:10 +0200
Message-ID<yTryG-1WY-13@gated-at.bofh.it>
In reply to#215277
Mark Allums wrote:

> On 10/19/2019 5:54 PM, Cindy Sue Causey wrote:
> > Hi, mike, I don't know, but, as soon as I read "Orca", I thought of
> > the Debian-Accessibility list:
> >
> > https://lists.debian.org/debian-accessibility/

Thanks, Cindy Sue, I may give that a try.

> I am not running Orca, but I have the same issue.

I poked around a little more and noticed that at-spi-dbus-launcher gets
started for both MATE and Xfce.  But there's no delay logging out from
Xfce.

So maybe this is worth filing a bug against mate-session-manager?

mike

[toc] | [prev] | [next] | [standalone]


#215327

FromJean-Philippe MENGUAL <jpmengual@debian.org>
Date2019-10-22 00:30 +0200
Message-ID<yTOlA-8it-21@gated-at.bofh.it>
In reply to#215301
Hi,

I realize I reproduce the bahivior described here. I dont know if
debian-accessibility was Cc but I do it. Let's what they say, but I
guess we should report a bug against at-spi itself.

The problem here is, indeed: at shutdown of Mate, "at-spi-bus-launcher
does not respond" and I can override te stop "reboot anywy".

Regards

-- 
Jean-Philippe MENGUAL

[toc] | [prev] | [next] | [standalone]


#215335

FromCurt <curty@free.fr>
Date2019-10-22 10:10 +0200
Message-ID<yTXoS-5Er-13@gated-at.bofh.it>
In reply to#215327
On 2019-10-21, Jean-Philippe MENGUAL <jpmengual@debian.org> wrote:
> Hi,
>
> I realize I reproduce the bahivior described here. I dont know if
> debian-accessibility was Cc but I do it. Let's what they say, but I
> guess we should report a bug against at-spi itself.
>
> The problem here is, indeed: at shutdown of Mate, "at-spi-bus-launcher
> does not respond" and I can override te stop "reboot anywy".

This daemon being difficult to extirpate with my kitchen-sink install,
and me being only disabled in ways addressed by neither at-spi nor
modern science, I resorted to removing the executable bit from 

 /usr/lib/at-spi2-core/at-spi2-registryd

and

 /usr/lib/at-spi2-core/at-spi-bus-launcher

to make my at-spi problem disappear (which wasn't the shutdown delay problem,
but another thing irrelevant to the current thread).

But then apps despairingly tried to register themselves with
an inexistent accessibility bus, so I set the "NO_AT_BRIDGE=1"
environment variable to head that off at the pass.

All probably highly inadvisable, but there you go.


> Regards
>


-- 
"There are no foreign lands. It is the traveler only who is foreign."
-- Robert Louis Stevenson

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web