On 10/13/2012 09:40 AM, Gerhard Brauer wrote:
> Sorry for maybe double-posting, fist sent with wrong from-address
> ;-)
>
> On Sat, Oct 13, 2012 at 04:34:04PM +0200, Tom Gundersen wrote:
>> On Sat, Oct 13, 2012 at 11:42 AM, Thomas Bächler <thomas@archlinux.org> wrote:
>>> Most (all?) of our login manager still depend on consolekit. However,
>>> since consolekit support will be stripped from polkit when
>>> gnome-unstable goes to testing (soon?), registering consolekit sessions
>>> on login has no effect whatsoever.
>>>
>>> Should we rebuild our login managers to remove the consolekit dependencies?
>>>
>>> I rebuilt kdebase-workspace locally yesterday, and polkit seems to work
>>> just fine. kde itself does not use consolekit, except through polkit.
>>
>> Doing this makes sense to me. However, to make things clear-cut, it
>> would be best if we could entirely remove consolekit from our repos
>> and put up an announcement. That way people will not be confused as to
>> why things stop working if they are not using logind.
>
> This makes me a little nervous…
> What are the way for people which ex. use fluxbox via
> ck-launch-session and thunar as a filemanager (for
> dbus/polkit/udisks things) AND NOT systemd-logind ?
>

I believe the logind equivalent to ck-launch-session is having

session required pam_loginuid.so
session required pam_systemd.so

in whatever pam service is being used: /etc/pam.d/{gdm,lightdm,sshd,...}.
pam_loginuid is not strictly necessary, but recommended.

> Will there be a way to use dbus/polkit-releated actions without
> systemd?
>
> I got more and more confused about the speed and amount of changes
> currently ;-)
>
>> Cheers,
>>
>> Tom
>
> Regards
> Gerhard
>
>

On Sat, Oct 13, 2012 at 5:14 PM, Matthew Monaco <dgbaley27@0x01b.net> wrote:
> I believe the logind equivalent to ck-launch-session is having
>
> session required pam_loginuid.so
> session required pam_systemd.so
>
> in whatever pam service is being used: /etc/pam.d/{gdm,lightdm,sshd,...}.
> pam_loginuid is not strictly necessary, but recommended.

Don't forget that if you're using startx you'll need to make sure the
vt X is using is the same one you logged in on:

startx -- vt1

Alternatively, one can craft a .xserverrc to automatically pass the
right vt option to X.


~Celti

Am 13.10.2012 17:40, schrieb Gerhard Brauer:
> What are the way for people which ex. use fluxbox via
> ck-launch-session and thunar as a filemanager (for
> dbus/polkit/udisks things) AND NOT systemd-logind ?

As Tom pointed out, it was an upstream decision by polkit to require
logind - without forking polkit, there is nothing we can do (and to be
honest, we have neither the manpower nor the motivation to do that). To
make matters worse, consolekit is (afaik) no longer developed.

This means (as was long announced) that all setups that use polkit will
soon require systemd.

On Sat, 13 Oct 2012 16:34:04 +0200
Tom Gundersen <teg@jklm.no> wrote:

> On Sat, Oct 13, 2012 at 11:42 AM, Thomas Bächler <thomas@archlinux.org>
> wrote:
> > Most (all?) of our login manager still depend on consolekit. However,
> > since consolekit support will be stripped from polkit when
> > gnome-unstable goes to testing (soon?), registering consolekit sessions
> > on login has no effect whatsoever.
> >
> > Should we rebuild our login managers to remove the consolekit dependencies?
> >
> > I rebuilt kdebase-workspace locally yesterday, and polkit seems to work
> > just fine. kde itself does not use consolekit, except through polkit.
>
> Doing this makes sense to me. However, to make things clear-cut, it
> would be best if we could entirely remove consolekit from our repos
> and put up an announcement. That way people will not be confused as to
> why things stop working if they are not using logind.
>
> In addition to the gnome+kde packages the relevant packages we would
> have to make sure still work without consolekit are:
>
> lxdm
> oblogout
> slim
> udiskie (optional)
> xfce4-session

xfce-session doesn't support systemd-logind at the moment. Please see the bug
report at <https://bugzilla.xfce.org/show_bug.cgi?id=8729>...

> xorg-xdm
>
> Cheers,
>
> Tom



--
Leonid Isaev
GnuPG key: 0x164B5A6D
Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D