[pulseaudio-discuss] dbus interface trouble

Chris Morgan chmorgan at gmail.com
Thu Jun 25 11:04:27 PDT 2015


Pulseaudio 6.0 here.

I was working on some code to interface to pulseaudio via module-dbus-protocol.

Recently upgrading to F22 has broken the code I had working, it looks
like org.PulseAudio.ServerLookup1 isn't present on the session bus. I
did notice that there is now a separate slice where the pulseaudio
server lives. Does anyone know how I'm supposed to reach this instance
in order to find the pulseaudio dbus server?

With the same code on an embedded system (built with yocto) I'm seeing
the same thing, no org.PulseAudio.ServerLookup1, except I'm running
the server as root.

In both cases it looks like the dbus-protocol module is loaded:

Module #11
Name: module-dbus-protocol
Usage counter: n/a
module.author = "Tanu Kaskinen"
module.description = "D-Bus interface"
module.version = "6.0-dirty"

I think I know why F22 isn't working with the F21 to F22 upgrade, but
I'm not sure why the embedded Linux setup of the same thing isn't

On the embedded side it looks like there is a socket file:

ls /var/run/pulse/ -l
srwxrwxrwx    1 pulse    pulse            0 Jun 25 15:14 dbus-socket
srwxrwxrwx    1 pulse    pulse            0 Jun 25 15:14 native
-rw-------    1 pulse    pulse            4 Jun 25 15:14 pid

Is there a different approach I should be taking to control volume
externally? The source app is a node app so dbus made sense vs. some
of the apparently unmaintained npm modules that could be used.


More information about the pulseaudio-discuss mailing list