On Mon, Mar 20, 2017 at 3:49 PM, Cristian Ionescu-Idbohrn <cristian.ionescu-idbo...@axis.com> wrote: > > On Sun, 19 Mar 2017, Felipe Sateler wrote: > > On Sun, Mar 19, 2017 at 6:26 PM, Cristian Ionescu-Idbohrn < > > cristian.ionescu-idbo...@axis.com> wrote: > > > On Sun, 19 Mar 2017, Felipe Sateler wrote: > > >> > > >> Control:tags -1 moreinfo > > >> > > >> On Sun, Mar 19, 2017 at 9:37 AM, Cristian Ionescu-Idbohrn > > >> <cristian.ionescu-idbo...@axis.com> wrote: > > >> > Package: pulseaudio > > >> > Version: 10.0-1 > > >> > Severity: normal > > >> > > > >> > I see these log messages: > > >> > > > >> > /var/log/user.log:Mar 18 22:43:50 debian pulseaudio[5682]: > > >> > [pulseaudio] module.c: module-combine is deprecated: Please use > > >> > module-combine-sink instead of module-combine! > > >> > /var/log/user.log:Mar 18 22:43:50 debian pulseaudio[5682]: > > >> > [pulseaudio] module-combine.c: We will now load module-combine-sink. > > >> > Please make sure to remove module-combine from your configuration. > > >> > > > >> > but I can't find any 'module-combine' reference in the configuration > > >> > files, neither under /etc/pulse nor ~/.pulse. I see though both libs: > > >> > > > >> > pulseaudio: /usr/lib/pulse-10.0/modules/module-combine-sink.so > > >> > pulseaudio: /usr/lib/pulse-10.0/modules/module-combine.so > > >> > > > >> > are distributed. My conclusion is that the deprecated module-combine > > >> > is loaded by default. What can I do to avoid seeing those messages? > > >> > > >> Do you have module-gconf loaded? It might have been loaded by > > >> configuraton set via paprefs. > > > > > > Yes, `pactl list' shows it: > > > > > > Module #12 > > > Name: module-gconf > > > Argument: > > > Usage counter: n/a > > > Properties: > > > module.author = "Lennart Poettering" > > > module.description = "GConf Adapter" > > > module.version = "10.0" > > > > Do you have set in paprefs "output to all devices"? > > How would I go about to find that out?
Open the paprefs program, and check if you have set the option to play to all devices. Disable that, and the warning should go away. -- Saludos, Felipe Sateler
