Evolution no longer starts

[Massimo B.]

I reproduced several times and can confirm…

Code: Select all

gdbus call --session --dest org.a11y.Bus --object-path /org/a11y/bus --method org.a11y.Bus.GetAddress

…always solves the issue and evolution starts fine after that.

[nikulinpi]

Lightdm starts its own DBUS instance for its own at-spi bus, and the session should be launching its own separate instance.

Session should not be using login manager's at-spi

[sMueggli]

I reproduced several times and can confirm…

Code: Select all

gdbus call --session --dest org.a11y.Bus --object-path /org/a11y/bus --method org.a11y.Bus.GetAddress

…always solves the issue and evolution starts fine after that.

Does $XDG_RUNTIME_DIR/at-spi/bus_0 exist before and/or after the gdbus call?

[Massimo B.]

Does $XDG_RUNTIME_DIR/at-spi/bus_0 exist before and/or after the gdbus call?

No it does not. After the gdbus call, the directory exists. Any idea what's wrong?

[Massimo B.]

Hi, I found another detail here (https://bugs.gentoo.org/903543#c13) from someone reporting it does only affect installations with evolution-ews. Are all of you affected by this issue also using EWS as part of Evolution?

Code: Select all

User        Window Manager(WM)      Desktop Environment(DE)     Display Server(DS)  Login Manager(LM)       Init        EWS
---------------------------------------------------------------------------------------------------------------------------
massimo     xfwm4                   Xfce-4.20                   Xorg                Lightdm                 Xorg        Yes
da51df      i3wm                    i3wm                        Xorg                Lightdm                 Sysvinit    ?
dumi        Marco                   Mate                        Xorg                Lightdm                 openrc      ?

[Massimo B.]

So my current workaround is just starting Firefox before Evolution.

Since today after some updates, this workaround does not work anymore and I need again this workaround to start evolution:

Code: Select all

gdbus call --session --dest org.a11y.Bus --object-path /org/a11y/bus --method org.a11y.Bus.GetAddress

[Massimo B.]

btw. that DBUS issue is not only affecting evolution. Also Xfce warns about that when doing...

Code: Select all

$ xfce4-panel --restart
(xfce4-panel:8349): dbind-WARNING **: 16:19:23.080: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1007/at-spi/bus_0: Permission denied

..but it does not fail like evolution does, maybe dbus is not absolutely required in this case.

[moniaqua]

Hi, I found another detail here (https://bugs.gentoo.org/903543#c13) from someone reporting it does only affect installations with evolution-ews. Are all of you affected by this issue also using EWS as part of Evolution?

Code: Select all

User        Window Manager(WM)      Desktop Environment(DE)     Display Server(DS)  Login Manager(LM)       Init        EWS
---------------------------------------------------------------------------------------------------------------------------
massimo     xfwm4                   Xfce-4.20                   Xorg                Lightdm                 Xorg        Yes
da51df      i3wm                    i3wm                        Xorg                Lightdm                 Sysvinit    ?
dumi        Marco                   Mate                        Xorg                Lightdm                 openrc      ?
moniaqua    xfwm4                   Xfce-4.20                   Xorg                Lightdm                 Sysvinit    No 

It's been a while since last post in this thread, but problem still exists here so I thought, I'd add to the list. I can start evolution with

Code: Select all

gdbus call --session --dest org.a11y.Bus --object-path /org/a11y/bus --method org.a11y.Bus.GetAddress

[Massimo B.]

Still my daily annoying workaround every morning. I like to avoid writing wrappers around the issue just to hide it and forget it, I prefer keeping it in mind and finding the solution one day. It's something around lightdm for sure, because the lightdm PID is getting into the failing contexts.

[Massimo B.]

Collecting all related upstream and Gentoo bug reports...

Maybe related:
https://bugzilla.redhat.com/show_bug.cgi?id=2162351
https://bugzilla.redhat.com/show_bug.cgi?id=2254965
https://gitlab.gnome.org/GNOME/epiphany ... te_1946293
https://gitlab.gnome.org/GNOME/at-spi2- ... issues/187
https://gitlab.gnome.org/GNOME/at-spi2- ... issues/180
https://github.com/canonical/lightdm/issues/394
https://forum.artixlinux.org/index.php?topic=6965.15
Gentoo:
https://bugs.gentoo.org/949238
https://bugs.gentoo.org/886485
https://bugs.gentoo.org/903543
https://bugs.gentoo.org/955954

We should decide on which ticket to focus.
Eventhough the issue only happens with lightdm, this might be not the fault of lightdm itself but only happening there, as ..180 reported the same issue when doing su - another-user.