Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

Antonio Russo antonio.e.russo at gmail.com
Fri Oct 13 15:11:13 BST 2017

On 10/13/17 09:27, Felipe Sateler wrote:
> On Fri, Oct 13, 2017 at 9:58 AM, Antonio Russo
> <antonio.e.russo at gmail.com> wrote:
>> On 10/13/17 07:30, Michael Biebl wrote:
>>> That seems like the wrong approach. sound.target does not have any
>>> dependencies on /tmp.
>>> If anything, it's pulseaudio which should ensure that /tmp is mounted.
>> I agree, wholeheartedly. But getting this directory out of /tmp has
>> been a bug for 7 years [1].
> Well, it's not usually a grave problem to have an empty dir in /tmp,
> so nobody gave it much priority

Yeah, I bumped my head on this because zfs mount will not, by
default, mount on top of a nonempty directory.

Honestly, I wouldn't have noticed otherwise.

> I think I have found the culprit. It is pulseaudio, because there is
> no suitable runtime dir, so it creates its own runtime dir in /tmp.
> Please try the following change: edit
> /lib/udev/rules.d/90-alsa-restore.rules , and change the alsactl lines
> to add a new flag:
> /usr/sbin/alsactl -E HOME=/run/alsa -E PULSE_RUNTIME_PATH=/run/alsa/runtime restore $attr{device/number}
> (and the same for the nrestore command).

Yep, that fixes it. Should this be reassigned to alsa-utils, then? This
probably also resolves pulseaudio bug 561777.

Antonio Russo

More information about the Pkg-systemd-maintainers mailing list