Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
0522 build of master on porter board
Description
Applications that make use of audio (and by default, pulseaudio as their backend) fail in various ways.
mixer fails with:
May 23 15:14:44 porter mixer[10167]: PaClient: connection failed: Connection refused
radio also fails attempting to connect to Pulseaudio
mediaplayer fails to play streams resulting in log messages from gstreamer's pulseaudio plugin:
Could not initialize supporting library.
It turns out that the pulseaudio daemon never starts:
root@porter:~# systemctl status --user pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; disabled; vendor preset: enabled) Active: inactive (dead)
Further, the pulseaudio socket activation unit is not enabled:
root@porter:~# systemctl status --user pulseaudio.socket ● pulseaudio.socket - Sound System Loaded: loaded (/usr/lib/systemd/user/pulseaudio.socket; disabled; vendor preset: enabled) Active: inactive (dead) Listen: /run/user/0/pulse/native (Stream)
I've confirmed on my 0512 build that pulseaudio is socket activated by reviewing the output of systemd-analyze and also noting that the server is running so something changed since that build date.
Attachments
Issue Links
- relates to
-
-
- Closed
-