Bug#854327: pulseaudio: default configuration depends on consolekit

[Felipe Sateler]

On Sun, Feb 19, 2017 at 7:17 PM, Michael Gilbert <mgilbert at debian.org> wrote:
> control: tag -1 - moreinfo
>
> On Mon, Feb 6, 2017 at 8:07 AM, Felipe Sateler wrote:
>> module-console-kit does nothing when systemd-logind is detected. If
>> it's failing for you then you do not have systemd (or the -shim)
>> installed and running.
>
> You are correct, I do not have systemd installed on this system, but
> then again it's kfreebsd so I can't.  However, the only thing standing
> in the way of working pulseaudio on kfreebsd is this consolekit error,
> which as I suggest below can be worked around in a couple ways.

Heh, kfreebsd doesn't really count as "default configuration".

>
>>> To fix this, either the "load-module module-console-kit" line can be
>>> commented in /etc/pulse/default.pa.  Or the consolekit package can be
>>> installed, but there are a lot of setups where it's not needed or
>>> wanted.
>>
>> But if you are not using the default settings, you can surely also
>> modify pulseaudio's configuration?  Or are you suggesting we drop
>> consolekit support entirely?
>
> I should have worded that paragraph more clearly.  Those are just a
> couple workarounds that can be used while the bug exists.  I have not
> thought about how to fix the problem generally.

The real fix is of course for consolekit module to exit gracefully if
consolekit is not installed (the logind module does the same). But I
have no idea how to do that. Would it be enough to check the dbus
error name? I can't find a canonical list of error names though....

-- 

Saludos,
Felipe Sateler