Bug 1479998 - pulseaudio daemon won't start if ~/.config/pulse/default.pa is non-empty
pulseaudio daemon won't start if ~/.config/pulse/default.pa is non-empty
Status: NEW
Product: Fedora
Classification: Fedora
Component: pulseaudio (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Lennart Poettering
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-08-09 17:52 EDT by Jonathan Wakely
Modified: 2017-08-09 17:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonathan Wakely 2017-08-09 17:52:53 EDT
Description of problem:

After upgrading to F26 my KDE Plasma desktop had no audio devices available. This turned out to be because the pulseaudio daemon would not start, writing this to the journal:

Aug 09 17:42:50 wraith.home pulseaudio[6869]: [pulseaudio] main.c: Module module-switch-on-port-available not loaded.
Aug 09 17:42:50 wraith.home pulseaudio[6869]: [pulseaudio] main.c: Failed to initialize daemon.
Aug 09 17:42:50 wraith.home pulseaudio[6866]: [pulseaudio] main.c: Daemon startup failed.

With F24 I disabled that module with a per-user config file:

$ cat ~/.config/pulse/default.pa
# unload-module module-switch-on-port-available

This config caused the daemon to exit on startup.

The daemon would not start even if the file only contains comments or empty lines.

The daemon only starts if the file is empty, or doesn't exist at all.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. pulseaudio --kill
2. echo > ~/config/pulse/default.pa
3. pulseaudio --start

Actual results:
E: [pulseaudio] main.c: Daemon startup failed.

Expected results:
Daemon starts successfully.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.