Mailinglist Archive: opensuse-factory (469 mails)

< Previous Next >
Re: [opensuse-factory] [openSUSE:Leap:15.2, Build 617.1] pulseaudio and systemd vs. setup-pulseaudio
01.04.2020 19:27, Manfred Hollstein пишет:
Hi there,

this is on build ID 617.1. I use the script setup-pulseaudio sometimes
to disable pulseaudio for a user session. This used to work without any
trouble (on Leap 15.1 at least), but today I still found two processes
running when logged in: "/usr/bin/pulseaudio --daemonize" and
"/usr/lib/pulse/gconf-helper". And indeed, running "pavucontrol" doesn't
hang/stop as it normally does when PA is disabled.

pavucontrol socket activates PA ...

%tmpfiles_create pulseaudio.conf
%{fillup_only -an sound}
if [ ! -f /etc/systemd/user/{name}.socket ]; then
echo "Switching PulseAudio activation using systemd user socket."
echo "Please log out from all sessions once to make it effective."
%systemd_user_post pulseaudio.socket
if [ ! -f /etc/systemd/user/{name}.socket ]; then
# below should work once when preset is defined properly:
# /usr/bin/systemctl --no-reload --global preset pulseaudio.socket
mkdir -p /etc/systemd/user/
ln -s %{_userunitdir}/%{name}.socket

And if preset will ever support global user activation, it will be
impossible to disable it. systemd does not offer any possibility to
disable units enabled globally (in /usr/lib/systemd).

As a consequence,
Kodi refuses to switch to a non-PA audio setup, hence playing back some
more enhanced video files and using audio passthrough is not possible.

I don't want to discuss the issue with audio passthrough etc., but my
main concern is "why does systemd always start up a pulseaudio daemon
when logging in" - even when PA is disabled.

To be honest, I don't know if this is a recent issue or if it existed in
earlier builds, too, but I just realised it due to another issue with
the 5.6 kernel not being able to do audio via HDMI anymore...

Does anybody have an idea? Bugzilla?

TIA, cheers.


< Previous Next >
Follow Ups