On Wed, 2011-10-12 at 12:23 +0300, Tanu Kaskinen wrote: [...] > I don't have any recollection of such discussion. If the session bus Must've confused it with something else, then. > starts after PA, then you'll lose the ability to use the the dbus server > discovery API (this makes it hard to use the dbus protocol), and the > ability to track the server existence on the session bus. For the > former, the solution is to remove the server discovery service from the > pulseaudio daemon, and make it a library and maybe also a small > standalone dbus service (and possibly also a binary that can be called > directly). For the latter, I'm not sure it's a huge problem that the > server isn't visible in the session bus in the rare(?) cases where the > session bus is launched after pulseaudio. I don't even know what is the > point of the server tracking in the session bus, but I know that > libpulse uses it for something. I believe that that something isn't > terribly important. I agree, which is why I pushed this out. Just wanted to see if there was some easy way to deal with the ramifications of someone starting PA in a console and then firing up X to get a session bus, etc. -- Arun
