Bug#844232: daisy-player: man page title is wrong if build directory isn't named ${package}-${version}

Paul Gevers wrote on Tue, Nov 15, 2016 at 20:31:33 +0100: > Hi Daniel, > > On 13-11-16 17:22, Daniel Shahaf wrote: > >Whilst working on the Reproducible Builds effort [0], we noticed > >that daisy-player could not be built reproducibly, due to `txt2man -p` > >parsing the last component of the

Bug#844232: daisy-player: man page title is wrong if build directory isn't named ${package}-${version}

Hi Daniel, On 13-11-16 17:22, Daniel Shahaf wrote: Whilst working on the Reproducible Builds effort [0], we noticed that daisy-player could not be built reproducibly, due to `txt2man -p` parsing the last component of the build directory. While upstream (thanks Jos) already accepted your

Re: At-SPI not started [mate]

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

Re: At-SPI not started [mate]

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. >

Re: At-SPI not started [mate]

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

Re: At-SPI not started [mate]

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]

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 **

Freeze of the tty

Hi all I'm experiencing an issue where I'm not sure how to debug it. I'm usually working on console 1. Every now and then I'm changing to another tty using Alt+F, most frequently to change to an X session or to a nspawn container. When I press Alt+F, the whole system locks. I can still use the