New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/lib/systemd/user/pulseaudio.service.d/30_qubes.conf ignored in Debian stretch #2644

Closed
adrelanos opened this Issue Feb 20, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@adrelanos
Member

adrelanos commented Feb 20, 2017

  • /lib/systemd/user/pulseaudio.service.d/30_qubes.conf
  • /lib/systemd/user/pulseaudio.socket.d/30_qubes.conf

These files are ignored at least in Debian stretch. Others untested.

As user user.

systemctl --user cat pulseaudio
# /usr/lib/systemd/user/pulseaudio.service
[Unit]
Description=Sound Service

[Service]
# Note that notify will only work if --daemonize=no
Type=notify
ExecStart=/usr/bin/pulseaudio --daemonize=no
Restart=on-failure

[Install]
Also=pulseaudio.socket
WantedBy=default.target

I don't know what these files are doing or if they are still required. Just randomly noticed, that its current implementation ignored on Debian stretch.

These probably would have to be moved to /usr/lib/systemd/user/.

marmarek added a commit to marmarek/old-qubes-core-agent-linux that referenced this issue Feb 21, 2017

systemd: place user dropins in /usr/lib instead of /lib
On non-Fedora those are not equivalent. On Debian, user units in /lib
are not supported

Reported by @adrelanos
Fixes QubesOS/qubes-issues#2644
@unman

This comment has been minimized.

Show comment
Hide comment
@unman

unman Feb 21, 2017

Member

I don't know if it's just in stretch- I've found it ridiculously hard to stop pulseaudio from starting up, at least in Debian, even following all the advice I've found (autospawn=no, dynamically disabling using alsa, pasuspend etc.). It comes back like Jason.
I'd purge it if I could but it's a dependency of qubes-gui-agent - why is that?

Member

unman commented Feb 21, 2017

I don't know if it's just in stretch- I've found it ridiculously hard to stop pulseaudio from starting up, at least in Debian, even following all the advice I've found (autospawn=no, dynamically disabling using alsa, pasuspend etc.). It comes back like Jason.
I'd purge it if I could but it's a dependency of qubes-gui-agent - why is that?

@marmarek marmarek referenced this issue in marmarek/old-qubes-core-agent-linux Feb 21, 2017

Merged

systemd: place user dropins in /usr/lib instead of /lib #89

marmarek added a commit to marmarek/old-qubes-core-agent-linux that referenced this issue Feb 21, 2017

systemd: place user dropins in /usr/lib instead of /lib
On non-Fedora those are not equivalent. On Debian, user units in /lib
are not supported

Reported by @adrelanos
Fixes QubesOS/qubes-issues#2644
@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Feb 21, 2017

Member

@unman I speculate the systemd user session keeps starting it.

Perhaps try this. Run as user.

systemctl --user mask pulseaudio

Would speculate that suffices (if that was the cause). Otherwise you could also try the following, but I would wonder if these are required.

systemctl --user mask pulseaudio.service
systemctl --user mask pulseaudio.socket
Member

adrelanos commented Feb 21, 2017

@unman I speculate the systemd user session keeps starting it.

Perhaps try this. Run as user.

systemctl --user mask pulseaudio

Would speculate that suffices (if that was the cause). Otherwise you could also try the following, but I would wonder if these are required.

systemctl --user mask pulseaudio.service
systemctl --user mask pulseaudio.socket
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment