[pulseaudio-discuss] Service File for running in system mode

Florian Lindner mailinglists at xgm.de
Sat Oct 8 13:50:24 UTC 2016

Am 06.10.2016 um 20:05 schrieb Felipe Sateler:
> On 6 October 2016 at 14:56, Florian Lindner <mailinglists at xgm.de> wrote:
>>>> Ok, so you mean adding a .socket file to that. I will try this later...
>>> Please also add a Requires=pulseaudio.socket to the service file so
>>> that it is always started (see the current user unit in git master)
>> I will, as soon as I add the socket file. I'm not really sure, isn't
>> that either the socket or the service file should be enabled, not both?
> Well, the Requires is merely to force the socket to always be active
> when the daemon is started. Otherwise if you start the daemon on its
> own and then you start the socket, it will fail. And there is not much
> benefit to not enabling the socket.
>>>> Do you have any idea what could be the problem with having the default
>>>> sink muted always? (see my other mail in this thread).
>>> This is a shot in the dark, but you may be racing with alsa-restore or
>>> alsa-state. Maybe you should add `After=alsa-state.service
>>> alsa-restore.service`? (On second thought, this sounds like a good idea anyway)
>> Mhh, I don't have any service files like alsa*.
>> Could it be because the $HOME of user pulse is /var/run/pulse which is
>> emptied at each boot? I don't really think so, so only files there are a
>> "native" socket file and "pid".
>> In /var/lib/pulse/ are the state files:
>> 0a95f82340cb4818a15b1fabc2ca2001-card-database.tdb
>> 0a95f82340cb4818a15b1fabc2ca2001-default-sink
>> 0a95f82340cb4818a15b1fabc2ca2001-default-source
>> 0a95f82340cb4818a15b1fabc2ca2001-device-volumes.tdb
>> 0a95f82340cb4818a15b1fabc2ca2001-stream-volumes.tdb
>> Any more ideas?
> No, sorry. A verbose log might have give clues.

Ok, I added --log-level=4 and rebooted.

The complete log (from boot until playing a stream on the muted device]
is available at: http://pastebin.com/V4N7ta0d

Maybe interesting is:

Okt 08 15:39:42 marduk pulseaudio[454]: could not open configuration
file /usr/share/alsa/ucm/Xonar STX/Xonar STX.conf
Okt 08 15:39:42 marduk pulseaudio[454]: error: could not parse
configuration for card Xonar STX
Okt 08 15:39:42 marduk pulseaudio[454]: error: failed to import Xonar
STX use case configuration -2
Okt 08 15:39:42 marduk pulseaudio[454]: UCM not available for card Xonar STX

Xonar STX is the card I want to use. When I saw this message the first
time, I deleted all files in pulse state directory /var/lib/pulse and
rebootet, but it still appears.

Is there maybe some race condition between kernel module loading for the
card (snd_virtuoso) and pulseaudio restore module?


More information about the pulseaudio-discuss mailing list