There are various situations where polkit_context_init() fails:
- PolicyKit daemon is not installed. This happens e. g. in a Debian or Ubuntu server installation (we split off the library to minimize dependencies)
- PolicyKit.conf does not exist or is invalid
However, I think that's too strong. Even without PK, CK is still useful for session tracking. If this happens, CK should behave as if it was compiled without PK support, not abort completely.
There are various situations where polkit_ context_ init() fails:
- PolicyKit daemon is not installed. This happens e. g. in a Debian or Ubuntu server installation (we split off the library to minimize dependencies)
- PolicyKit.conf does not exist or is invalid
Right now, CK aborts with
Sep 28 22:10:01 acheron console- kit-daemon[ 13695]: CRITICAL: cannot initialize libpolkit
However, I think that's too strong. Even without PK, CK is still useful for session tracking. If this happens, CK should behave as if it was compiled without PK support, not abort completely.