Re: Some ALSA apps stopped working [REALLY SOLVED]
Florian Kulzer wrote:
> On Tue, Jul 10, 2007 at 10:30:15 +0100, Chris Lale wrote:
>
> [...]
>
>> Problem solved. alsaconf runs the obsolete command "update-modules" which
>> modifies /etc/modprobe.d/sound and /etc/modprobe.conf if present. According to
>> the update-modules man page the existence of /etc/modprobe.conf will cause
>> /etc/modprobe.d/ to be ignored by Debian packages which store their
>> configuration files there.
>
> [...]
>
>> I am not sure why /etc/modprobe.conf existed. Probably because my Etch (Stable)
>> system has been incrementally upgraded from Woody (Stable) and Etch (Testing).
>>
>> Worth reporting as a bug, do you think?
>
> I would say so; the manpage of update-modules is pretty clear about it:
>
> "Any program calling [update-modules] should be fixed."
I have reported this as a bug [1], but the initial response is not encouraging
("Hey you guys out there, why are you using alsaconf?").
>
> (It is nice that this possible pitfall is now documented in the list
> archives.)
>
I have also summarised this thread on the NewbieDOC wiki [2].
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432678
[2]
http://newbiedoc.berlios.de/wiki/Sound_in_Debian_GNU/Linux#Some_applications_.28OSS_applications.29_produce_no_sound_in_ALSA
--
Chris.
Reply to: