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@xxxxxxxxxxxxx> 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
>
>
