https://bugs.freedesktop.org/show_bug.cgi?id=54029
--- Comment #12 from Tanu Kaskinen <[email protected]> 2012-09-05 06:22:53 UTC --- My guess is that when libasound reads the configuration too early, the configuration is somehow not ready yet, and the unfinished configuration is then cached by libasound so that as long as libasound is being linked to the pulseaudio process, the configuration never gets updated. Once you unload all modules that use libasound (i.e. all module-alsa-card instances), then libasound gets unlinked too from the pulseaudio process. Subsequent loading of module-alsa-card works, because now libasound properly reloads the configuration which is ready at this point. So, I blame alsa for everything... That's based on guessing only, though, so I'll keep this bug open here at PulseAudio side too, in case someone wants to dig deeper. You can report the problem on the alsa-devel mailing list. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. You are the assignee for the bug. _______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
