On 2017-01-04 20:05, Tanu Kaskinen wrote: > On Wed, 2017-01-04 at 19:57 +0100, Linux User #330250 wrote: >> The one thing that remains unclear to me so far is how it autoloads in >> the first place, because I cannot find any raop modules in the config >> files in /etc/pulse. I assume that module-raop-discover does the magic, >> but it does it wrong, so I would like to blacklist this module and >> manually load the modules-raop-sink instead. Only, I couldn't find a >> blacklist syntax for default.pa (or system.pa). I found >> "disallow-module-loading true" which prevents all module loading. I >> could try unload-module, but how will this prevent a later invoked >> automatic module loading? I hope that the manual line in >> /etc/pulse/default.pa will prevent the module-raop-discover magic from >> now on, otherwise I can only think of renaming module-raop-discover in >> the file system. > module-raop-discover is loaded by module-gconf, which is a module that > is only used for interfacing with paprefs. So that bit of configuration > is stored in gconf (yes, not a very nice system). You enabled raop with > paprefs, and you should be able to disable it with paprefs too. > This would have been the last place for me to look. And, yes, I manually (deliberately) enabled it there... but forgot that I did. Using paprefs I disabled it now. Thanks again for your help!
