On Mon, May 09, 2016 at 09:52:41PM +0200, Michał Mirosław wrote: > On Mon, May 09, 2016 at 02:31:11PM +0200, Elimar Riesebieter wrote: > > * Michał Mirosław <mirq-bo...@rere.qmqm.pl> [2016-05-09 12:07 +0200]: > > > > > On Sun, May 08, 2016 at 05:14:30PM +0200, Elimar Riesebieter > > > wrote: > > > > * Michał Mirosław <mirq-bo...@rere.qmqm.pl> [2015-10-22 08:46 > > > > +0200]: > > > > > > > > > Package: libasound2 Version: 1.0.28 Severity: normal Tags: > > > > > patch > > > > > > > > > > --- Please enter the report below this line. --- > > > > > > > > > > 'aplay -L' segfaults with ALSA configuration containing > > > > > multiple "@hooks" entries. This happens, eg. with > > > > > libasound2-plugins installed and having one @hooks in > > > > > /etc/asound.conf like following: > > > > > > > > > > @hooks [ { func load files [ "/usr/share/alsa/bluetooth.conf" > > > > > ] errors false } ] > > > > > > > > I can reproduce this segfault. Well, > > > > /usr/share/alsa/bluetooth.conf isn't distributed by any Debian > > > > package and is not available in my default installation. Do you > > > > installed that file? Anyway, what is your goal with that hook? > > > > > > Hmm. This comes from bluez-alsa package - it seems this was left > > > after an upgrade from wheezy (the file is from bluez-alsa > > > package). This seems irrelevant, though, as you should be able to > > > trigger the bug with any two files. > > > > Wrong, if I use the existing /usr/share/alsa/smixer.conf instead of > > /usr/share/alsa/bluetooth.conf there is no segfault. > > > > Could you please provide your bluetooth.conf? > That's the one from wheezy's bluez-alsa (version 4.99-2). Attached.
BTW, for me, it's enough to put: @hooks [ { func load files [ "/dev/null" ] } ] in /etc/asound.conf to make 'aplay -L' blow up. Best Regards, Michał Mirosław