Re: At-SPI not started [mate]

2016-11-15 Thread Sebastian Humenda
Hi Samuel Thibault schrieb am 15.11.2016, 19:37 +0100: >Sebastian Humenda, on Tue 15 Nov 2016 19:25:05 +0100, wrote: >> Samuel Thibault schrieb am 15.11.2016, 14:09 +0100: >> >Sebastian Humenda, on Tue 15 Nov 2016 11:53:29 +0100, wrote: >> >> After an update, >> > >> >Which update, when? Please b

Re: At-SPI not started [mate]

2016-11-15 Thread Samuel Thibault
Hello, Sebastian Humenda, on Tue 15 Nov 2016 19:25:05 +0100, wrote: > Samuel Thibault schrieb am 15.11.2016, 14:09 +0100: > >Sebastian Humenda, on Tue 15 Nov 2016 11:53:29 +0100, wrote: > >> After an update, > > > >Which update, when? Please be specific, that is very precious > >information. > I'

Re: At-SPI not started [mate]

2016-11-15 Thread Sebastian Humenda
Hi Samuel Thibault schrieb am 15.11.2016, 14:09 +0100: >Sebastian Humenda, on Tue 15 Nov 2016 11:53:29 +0100, wrote: >> After an update, > >Which update, when? Please be specific, that is very precious >information. I've updated my testing machine on the 15th. I'm not sure what broke at-spi and a

Re: At-SPI not started [mate]

2016-11-15 Thread Samuel Thibault
Hello, Sebastian Humenda, on Tue 15 Nov 2016 11:53:29 +0100, wrote: > After an update, Which update, when? Please be specific, that is very precious information. Samuel

At-SPI not started [mate]

2016-11-15 Thread Sebastian Humenda
Hi After an update, at-spi is not started automatically anymore. This leads to an inaccessible mate session. Launching `orca -r` gives: ``` ** (orca:7169): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-TU92PCmRzt: Verbindungsaufbau abgelehnt ** (orca:7