OS: Arch Pulseaudio version: 7.0 Since upgrading to pulseaudio 7.0 my per-user client.conf is not being read anymore, or something undocumented has changed with the directives i'm using. I'm using it to disable gdm's pulseaudio daemon. $ grep gdm /etc/passwd gdm:x:120:120:Gnome Display Manager:/var/lib/gdm:/sbin/nologin $ cat cat /var/lib/gdm/.config/pulse/client.conf autospawn = no daemon-binary = /bin/false Worked fine in pulseaudio 6.0
Weird. I wonder if PA is looking in a different directory. You could put "extra-arguments = --log-target=newfile:/tmp/pulse.log --log-level=debug" to /etc/pulse/client.conf and reboot. Then attach the log to this bug. That should show what directory gdm's PulseAudio is using for configuration.
I seem to recall an intentional change that caused first start to succeed even when autospawn=no was set, but I can't find it.
Might arch have enabled the systemd user units?
Adding Jan Steffens to CC. IIRC, he's the Arch PulseAudio maintainer. Jan, does Arch use systemd socket activation with PulseAudio? I remember we talked about the topic in IRC, but I'm not sure if you enabled it in the official packages.
Yes, it is enabled now, as we have user buses.
So, try linking /var/lib/gdm/.config/systemd/user/pulseaudio.service and .socket to /dev/null .
OK so it is the systemd user unit that is starting it. Jan's suggestion with linking it to /dev/null disabled the unit for the user. The question still stands though: shouldn't the client.conf be read by pulseaudio when it's being started like this? It seems that even the global client.conf is not being read. i.e. adding "extra-arguments = --log-target=newfile:/tmp/pulse.log --log-level=debug" didn't do anything and doesn't show up in `ps aux | grep pulse`. All i can see is what's defined in the systemd unit (/usr/bin/pulseaudio --daemonize=no)
No, it shouldn't. client.conf is read by libpulse, not systemd or the pulseaudio server. Hence, 'autospawn', 'daemon-binary' and 'extra-arguments' only affect libpulse's autospawning. Also, a user's client.conf completely overrides any global client.conf.
Closing bug.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.