ConsoleKit 0.2.4

Matthias Clasen matthias.clasen at
Wed Jan 23 19:05:57 PST 2008

On Jan 23, 2008 9:05 PM, Michael Biebl <mbiebl at> wrote:

> I still see no reason why this should be put into CK. Wasn't CK about
> tracking user sessions and seats? Imo this functionality doesn't
> belong into CK.

One reason is that you want to use knowledge about sessions and logged
in users when deciding how to respond to a reboot request, e.g. don't
allow the reboot right away when there are multiple active sessions
(well, maybe allow it anyway if all the other sessions are xdmcp
sessions). This information already lives in ConsoleKit, so
it seems like a good place to handle the reboot request.

> > > This also creates a very "nice" dependency loop:
> > > CK depending on PolicyKit and PolicyKit depending on CK. Not good.
> >
> > There is no dependency loop.  ConsoleKit requires libpolkit only.
> > libpolkit does not require ConsoleKit or D-Bus.
> Well, just check your fedora packages then [1]:
> The PolicyKit package has a requires ConsoleKit.
> And as the PK package ships libpolkit, ConsoleKit will have a requires
> PolicyKit.
> Such dependency loops are bad.

Cyclic dependencies are a fact of life, and while annoying, they are
not the end
of the world. And as you point out, this one can be easily avoided by
splitting the PolicyKit package.

More information about the hal mailing list