Bug#921068: enlightenment: Crashes when failing to load ALSA on start up.

Ross Vandegrift ross at kallisti.us
Sun Feb 3 17:06:26 GMT 2019

Control: forwarded -1 https://phab.enlightenment.org/T7680

On Sat, Feb 02, 2019 at 07:34:13PM -0800, Ross Vandegrift wrote:
> On Fri, Feb 01, 2019 at 09:59:46AM +0100, Nicolas Cavallari wrote:
> > (The original ALSA problem is that the documented way to disable
> >  redirecting ALSA applications to pulseaudio was to divert
> >  /usr/share/alsa/alsa.conf.d/pulse.conf away)
> There is a recent patch in upstream git that sounds like it could be related
> (a841544d0).  I hope to have some time to test tomorrow.

After a second a look, this patch won't help.

The problem is that your dpkg-divert leaves alsa with an invalid config:
$ amixer info
ALSA lib conf.c:3639:(config_file_open) cannot access file /etc/alsa/conf.d/99-pulse.conf
ALSA lib conf.c:3559:(snd_config_hooks_call) function snd_config_hook_load returned error: No such file or directory
ALSA lib conf.c:4013:(snd_config_update_r) hooks failed, removing configuration
amixer: Control device default open error: No such file or directory

According to #915696, configs in /usr/share/alsa/alsa.conf.d are no longer
automatically loaded.  So now you want to remove your diversion and delete the
symlink in /etc instead.

Still, mixer should handle cases when its backend fails to initialize.


More information about the Pkg-e-devel mailing list