At Fri, 22 Jul 2011 21:49:08 +0200,
Julien Cristau wrote:
> 
> > +   display_device = devtmp;
> > +    }
> > +
> > +    connector = ck_connector_new();
> > +    if (!connector) {
> > +   LogOutOfMem("ck_connector");
> > +   return 0;
> > +    }
> > +
> > +    dbus_error_init(&error);
> > +    ret = ck_connector_open_session_with_parameters(
> > +           connector, &error,
> > +           "unix-user", &verify->uid,
> > +           "x11-display", &display_name,
> > +           "x11-display-device", &display_device,
> > +           "remote-host-name", &remote_host_name,
> > +           "is-local", &is_local,
> > +           NULL);
> > +    if (!ret) {
> > +   if (dbus_error_is_set(&error)) {
> > +       LogError("Dbus error: %s\n", error.message);
> > +       dbus_error_free(&error);
> > +   } else {
> > +       LogError("ConsoleKit error\n");
> > +   }
> > +   LogError("console-kit-daemon not running?\n");
> > +   ck_connector_unref(connector);
> > +   connector = NULL;
> > +   return 0;
> 
> Is "ck-daemon isn't running" a good reason to prevent the user from
> logging in?  (Why?)

It's reached only when you set use_consolekit is set.  You say you
are using CK but it's not detected, thus it's an error.


thanks,

Takashi
_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to