Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-29 Thread Felipe Sateler
On Fri, Jun 29, 2018 at 3:26 AM Mike Brodbelt wrote: > On 29/06/18 04:26, Felipe Sateler wrote: > > > Thanks. However, it has some flaws that need to be reworked for this to > > work at all: > > > > 1. We can't rely on gcc being installed > > Would "dpkg-architecture -qDEB_BUILD_MULTIARCH" be a

Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-29 Thread Mike Brodbelt
On 29/06/18 04:26, Felipe Sateler wrote: Thanks. However, it has some flaws that need to be reworked for this to work at all: 1. We can't rely on gcc being installed Would "dpkg-architecture -qDEB_BUILD_MULTIARCH" be a reasonable replacement? 2. It doesn't check /proc is actually mounted

Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-28 Thread Felipe Sateler
Hi Mike, On Thu, Jun 28, 2018 at 6:15 PM Mike Brodbelt wrote: > On 21/06/18 12:34, Felipe Sateler wrote: > > > Patches welcome. If you decide to implement this, make sure that the > > code is only active with a running sysvinit (ie, don't affect chroots). > > It is not trivial, which is why I

Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-28 Thread Mike Brodbelt
On 21/06/18 12:34, Felipe Sateler wrote: Patches welcome. If you decide to implement this, make sure that the code is only active with a running sysvinit (ie, don't affect chroots). It is not trivial, which is why I didn't implement it myself. You probably need to integrate ucf to handle all

Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-21 Thread Felipe Sateler
On Wed, Jun 20, 2018, 19:51 Mike Brodbelt wrote: > On 19/06/18 02:35, Ross Vandegrift wrote: > > > While upgrading a different machine from stretch -> buster, I noticed > > the following in apt-listchanges output: > > > > pulseaudio (11.1-2) unstable; urgency=medium > > > >* Since this

Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-20 Thread Mike Brodbelt
On 19/06/18 02:35, Ross Vandegrift wrote: While upgrading a different machine from stretch -> buster, I noticed the following in apt-listchanges output: pulseaudio (11.1-2) unstable; urgency=medium * Since this version, pulseaudio disables autospawn by default on linux systems, and

Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-18 Thread Ross Vandegrift
On Fri, Jun 15, 2018 at 12:48:51AM +0100, Mike Brodbelt wrote: > $ cd ~ && grep autospawn .config/pulse/client.conf /etc/pulse/client.conf > grep: .config/pulse/client.conf: No such file or directory > /etc/pulse/client.conf:; autospawn = yes > > It's possible this is a bug in pulseaudio

Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-15 Thread Ross Vandegrift
Control: reassign -1 pulseaudio On Fri, Jun 15, 2018 at 12:48:51AM +0100, Mike Brodbelt wrote: > > > $ start-pulseaudio-x11 > > > Connection failure: Connection refused > > > pa_context_connect() failed: Connection refused > > > > This is curious. According to start-pulseaudio-x11(1), it should

Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-12 Thread Ross Vandegrift
On Tue, Jun 05, 2018 at 11:01:35PM +0100, Mike Brodbelt wrote: > Doing some investigation into this, I enabled "PulseAudio Sound System" > in Settings > Apps > Startup Applications. This didn't work - it seems > to execute 'start-pulseaudio-x11' at login, which fails because it's > executed at a

Bug#900856: enlightenment: Sound fails to work after upgrade

2018-06-05 Thread Mike Brodbelt
Package: enlightenment Version: 0.22.1-3 Severity: normal After upgrading from the venerable e17 package, sounds stopped working entirely on my desktop. I am not 100% certain whether the situation here is a bug in the Enlightenment package, or elsewhere, but I'm filing it here as it was triggered