<div dir="ltr"><div>HI! </div><div>I must say that the system is now working as expected. <div class="gmail-post-text">Problem was in <a href="http://system.pa">system.pa</a>. I found in manual that in system wide daemon configuration should not use automatic detection. from pulseaudio manual pages: <pre><code> --disallow-module-loading[=BOOL] Disallow module loading after startup. This is a security feature since it disallows additional module loading during runtime and on user request. It is highly recommended when --system is used (see above). Note however, that this breaks certain fea‐ tures like automatic module loading on hot plug. </code></pre> So I disabled (commented) lines from <a href="http://system.pa">system.pa</a> <pre><code> ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else #### Use the static hardware detection module (for systems that lack udev/hal support) #load-module module-detect #.endif </code></pre> and now works. </div></div>Thanks! </div><div class="gmail_extra"> <div class="gmail_quote">On Sat, Mar 18, 2017 at 9:54 PM, Anton Lundin <<a href="mailto:glance@acc.umu.se" target="_blank">glance@acc.umu.se</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 18 March, 2017 - Tadej Panjtar wrote: > Thanks! > ... > > If PA is started via command as root it works. But if same command > is run via systemd, happens Got signal SIGTERM. > Here is log. ... > mar 18 00:14:11 tadejas pulseaudio[8285]: Got signal SIGTERM. ... > and here is service script: > > # systemd service spec for pulseaudio running in system mode -- not > recommended though! > # put it under /etc/systemd/system/pulseaudio.service > # start with: systemctl start pulseaudio.service > # enable on boot: systemctl enable pulseaudio.service > > [Unit] > Description=Plseaudio Service > After=network-online.target > > [Service] > ExecStart=/usr/bin/pulseaudio -vvvv --system --disallow-exit > --disallow-module-loading > #ExecReload=/bin/kill -HUP $MAINPID > TimeoutSec=13 I guess this is your problem. 13 seconds after start systemd sends a SIGTERM, because it thinks the service didn't start properly. //Anton > > [Install] > WantedBy=multi-user.target > > Best regards, > Tadej > > > > On Fri, Mar 17, 2017 at 3:16 AM, Arun Raghavan <<a href="mailto:arun@arunraghavan.net">arun@arunraghavan.net</a>> > wrote: > > > On Wed, 15 Mar 2017, at 12:27 PM, Tadej Panjtar wrote: > > > Hi! > > > > > > I Migrated from pulseaudio version 4.0 to 8.0 and the following command > > > does not work anymore: > > > load-module module-alsa-sink device="hw:2,7" sink_name=seat1 > > > > > > E: [pulseaudio] module.c: Failed to load module "module-alsa-sink" > > > (argument: "device="hw:2,7" sink_name=seat1"): initialization failed. > > > E: [pulseaudio] main.c: Module load failed. > > > > > > What is wrong? > > > > You need to increase your pulseaudio debug level (or start it with > > -vvvv). > > > > -- Arun > > > _______________________________________________ > pulseaudio-discuss mailing list > <a href="mailto:pulseaudio-discuss@lists.freedesktop.org">pulseaudio-discuss@lists.freedesktop.org</a> > <a href="https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss</a> -- Anton Lundin <a href="tel:%2B46702-161604" value="+46702161604">+46702-161604</a> _______________________________________________ pulseaudio-discuss mailing list <a href="mailto:pulseaudio-discuss@lists.freedesktop.org">pulseaudio-discuss@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss</a> </blockquote></div> </div>