Re: [arch-general] [arch-dev-public] consolekit dependencies?
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 ? 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:40 PM, Gerhard Brauer <gb+ML-2011@derbrauer.homelinux.net> wrote:
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 ?
Will there be a way to use dbus/polkit-releated actions without systemd?
No. Since polkit will soon only work when the system is booted with systemd, the usefulness of consolekit is very limited. To minimize the confusion we will therefore remove CK completely (of course if anyone decides to create third-party packages as I proposed in the past [0] it could still be possible to keep CK+polkit without systemd).
I got more and more confused about the speed and amount of changes currently ;-)
There has been a lot of discussion about this on the ML. I remember polkit losing CK support was discussed when the move to systemd was first proposed [1], and I brought it up again in the proposal for keeping sysvinit working [0]. You might find more background discussion if you search our archives. There was at some point an attempt at trying to make polkit work with CK and systemd both [3], but it didn't go anywhere and the patch was rejected upstream. [0]: <http://www.mail-archive.com/arch-general@archlinux.org/msg31229.html> [1]: <http://www.mail-archive.com/arch-dev-public@archlinux.org/msg19796.html> [2]: <http://www.mail-archive.com/arch-general@archlinux.org/msg29297.html>
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.
participants (5)
-
Gerhard Brauer
-
Matthew Monaco
-
Patrick Burroughs (Celti)
-
Thomas Bächler
-
Tom Gundersen