Bug#992856: pulseaudio: Pulseaudio does not automatically start on newer kernel

[Pierre-Yves Luyten]

Package: pulseaudio
Version: 14.2-2
Severity: normal

Since upgrade to bullseye, I noticed pulseaudio is not automatically started.
For example in GNOME preferences sound preferences are empty, pavucontrol does
not start.

If i manually start pulseaudio like below, then i can see the sound
preferences, or use pa related tools.
$ pulseaudio

I run into the default kernel.

# uname -r
5.10.0-8-amd64

I noticed if i boot under an older kernel, pulseaudio is started automatically,
the bug does not happen. I picked a random one for testing, linux-
image-4.19.0-17-amd64.

Please tell me what additional information could i provide to help?


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii adduser 3.118
ii init-system-helpers 1.60
ii libasound2 1.2.4-1.1
ii libasound2-plugins 1.2.2-2
ii libc6 2.31-13
ii libcap2 1:2.44-1
ii libdbus-1-3 1.12.20-2
ii libgcc-s1 10.2.1-6
ii libice6 2:1.0.10-1
ii libltdl7 2.4.6-15
ii liborc-0.4-0 1:0.4.32-1
ii libpulse0 14.2-2
ii libsm6 2:1.2.3-1
ii libsndfile1 1.0.31-2
ii libsoxr0 0.1.3-4
ii libspeexdsp1 1.2~rc1.2-1.1
ii libstdc++6 10.2.1-6
ii libsystemd0 247.3-6
ii libtdb1 1.4.3-1+b1
ii libudev1 247.3-6
ii libwebrtc-audio-processing1 0.3-1+b1
ii libx11-6 2:1.7.2-1
ii libx11-xcb1 2:1.7.2-1
ii libxcb1 1.14-3
ii libxtst6 2:1.2.3-1
ii lsb-base 11.1.0
ii pulseaudio-utils 14.2-2

Versions of packages pulseaudio recommends:
ii dbus-user-session 1.12.20-2
ii libpam-systemd [logind] 247.3-6
pn rtkit <none>

Versions of packages pulseaudio suggests:
pn paprefs <none>
ii pavucontrol 4.0-2
pn pavumeter <none>
ii udev 247.3-6

-- no debconf information

[Marco Balmer]

Package: pulseaudio
Version: 14.2-2
Followup-For: Bug #992856

I confirm this bug.

After starting pulseaudio manually
$ pulseaudio --start
audio is working.

How can I workarround this problem?

-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)

Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash

ii rtkit 0.13-4

Versions of packages pulseaudio suggests:
pn paprefs <none>

pn pavucontrol <none>

[Marco Balmer]

# ls -l /etc/pulse/client.conf.d/01-enable-autospawn.conf
lrwxrwxrwx 1 root root 32 26. Feb 2021 /etc/pulse/client.conf.d/01-
enable-autospawn.conf -> /run/pulseaudio-enable-autospawn
# ls -l /run/pulseaudio-enable-autospawn
ls: cannot access '/run/pulseaudio-enable-autospawn': No such file or
directory

Could this be the cause of the problem?

Thanks,
Marco

[Pierre-Yves Luyten]

Hello,

sorry i missed your previous question.

I was fixing an issue where login is very long on my system, and
ameneded nftables.

iif lo tcp dport { 9050, 9150 } log prefix SYSTEMD-BUG- reject


And actually fixing this issue also makes pulse audio start normally
now. So, sorry it was a side effect.

Pierre-Yves

[Marco Balmer]

Hello,

My current workaround is:

/etc/profile.d/fix-pulseaudio.sh:

if ! pidof pulseaudio >/dev/null;
then
echo workaround pulseaudio started
pulseaudio --start &
fi

On which systemd version (package) is this fixed from your point of
view?

Marco

$ dpkg -l pulseaudio systemd
ii pulseaudio 14.2-2 amd64 PulseAudio sound server
ii systemd 247.3-6 amd64 system and service manager

On Sun, 28 Nov 2021 11:58:07 +0100 Pierre-Yves Luyten <p...@luyten.fr>
wrote: