Re: [DNG] elogind testing for experimental and ascii-proposed

Hi all, I am trying consolekit2 and getting screen locked with KDE on ascii. To unlock it needs loginctl unlock-sessions ut I cannot find it in my system. Does anyone know how to fix that? On 20 January 2018 at 19:28, KatolaZ wrote: > On Sat, Jan 20, 2018 at 11:46:33AM

Re: [DNG] elogind testing for experimental and ascii-proposed

On Sat, Jan 20, 2018 at 11:46:33AM +0100, Andreas Messer wrote: [cut] > > So my oppinion is, that, at least for transition or migration purposes > we need to provide two paths in devuan, the user needs to choose one of them > > - consolekit(2) + policykit > - elogind + policykit-logind >

Re: [DNG] elogind testing for experimental and ascii-proposed

Hello all, sorry for beeing mute for so long, but i was busy with other things, and still have not much time at the moment On Fri, Jan 19, 2018 at 11:48:43AM +0100, Irrwahn wrote: > Andreas Messer wrote on 19.01.2018 07:16: > > That seems strange. loginctl is a elogind command and when elogind

Re: [DNG] elogind testing for experimental and ascii-proposed

Le 20/01/2018 à 01:01, Adam Borowski a écrit : On Fri, Jan 19, 2018 at 02:29:58PM -0800, Rick Moen wrote: The only real solution is to do without the Freedesktop.org 'stack' and give GNOME the heave-ho. Devuan appears unwiling to take that step so far, therefore here you are, adopting Gentoo's

Re: [DNG] elogind testing for experimental and ascii-proposed

On 19.01.18 17:34, KatolaZ wrote: > On Fri, Jan 19, 2018 at 06:03:59PM +0100, Didier Kryn wrote: > >     But wether that session is local or not is, in my opinion, and as I > > already said, futile; and it seems to be mostly used as a justification to > > develop a tangle of daemons and middleware

Re: [DNG] elogind testing for experimental and ascii-proposed

Quoting Adam Borowski (kilob...@angband.pl): > While I heartily agree with you about GNOME itself, there's too much > software that uses gnome libs to allow such a move without having to patch > hundreds if not thousands of packages. Last time I checked, the GNOME libs required by 90%+ of those

Re: [DNG] elogind testing for experimental and ascii-proposed

On Fri, Jan 19, 2018 at 02:29:58PM -0800, Rick Moen wrote: > The only real solution is to do without the Freedesktop.org 'stack' and > give GNOME the heave-ho. Devuan appears unwiling to take that step so > far, therefore here you are, adopting Gentoo's systemd-logind forked > code (which is what

Re: [DNG] elogind testing for experimental and ascii-proposed

Quoting KatolaZ (kato...@freaknet.org): > Devuan is not adopting anything atm. Those packages are in > experimental, that is a repo meant for experimentations and tests. Noted. Thank you for clarifying (and yes, that was also stressed in the Subject header). > The mistake made by Debian was

Re: [DNG] elogind testing for experimental and ascii-proposed

On Fri, Jan 19, 2018 at 02:29:58PM -0800, Rick Moen wrote: [cut] > > The only real solution is to do without the Freedesktop.org 'stack' and > give GNOME the heave-ho. Devuan appears unwiling to take that step so > far, therefore here you are, adopting Gentoo's systemd-logind forked > code

Re: [DNG] elogind testing for experimental and ascii-proposed

On Fri, Jan 19, 2018 at 02:29:58PM -0800, Rick Moen wrote: [cut] > > The only real solution is to do without the Freedesktop.org 'stack' and > give GNOME the heave-ho. Devuan appears unwiling to take that step so > far, therefore here you are, adopting Gentoo's systemd-logind forked > code

Re: [DNG] elogind testing for experimental and ascii-proposed

Quoting Arnt Karlsen (a...@iaksess.no): > ..so a good way forward is, treat this policykit/consolekit/logind > etc thing like systemd, pulseaudio etc poetterware. I'm bemused by people in the Devuan Project wanting to find a compatible substitute for systemd-logind. The entire Debian fiasco was

Re: [DNG] elogind testing for experimental and ascii-proposed

On Fri, Jan 19, 2018 at 09:52:03PM +0100, Irrwahn wrote: [cut] > > All in all, I think that looks somewhat promising. However, as KatolaZ > rightly > pointed out, it'd be important to know which other setups would possibly be > broken by that approach, and what issues in other DEs might

Re: [DNG] elogind testing for experimental and ascii-proposed

Hleb Valoshka wrote on 19.01.2018 20:44: > On 1/19/18, Irrwahn wrote: >> I think that has to be done anyway, because currently one cannot >> have policykit without having consolekit installed with it, due to >> the "Depends". The package should have something akin to: >> >>

Re: [DNG] elogind testing for experimental and ascii-proposed

On 1/19/18, Irrwahn wrote: > I think that has to be done anyway, because currently one cannot > have policykit without having consolekit installed with it, due to > the "Depends". The package should have something akin to: > > Depends: libpam-elogind | consolekit > > Anyone

Re: [DNG] elogind testing for experimental and ascii-proposed

KatolaZ wrote on 19.01.2018 19:05: > On Fri, Jan 19, 2018 at 06:48:42PM +0100, Irrwahn wrote: > > [cut] > >> >> In my mind, the whole mess looks more like a gigantic game of nuclear >> whack-a-mole, and the only winning move is not to play. (The optimist >> believes we are living in the best of

Re: [DNG] elogind testing for experimental and ascii-proposed

Le 19/01/2018 à 18:34, KatolaZ a écrit : On Fri, Jan 19, 2018 at 06:03:59PM +0100, Didier Kryn wrote: [cut]     I think the concept of session is still usefull in the framework of a Desktop Environment. When you log into that kind of environment, you have a few services associated to it

Re: [DNG] elogind testing for experimental and ascii-proposed

On Fri, Jan 19, 2018 at 06:48:42PM +0100, Irrwahn wrote: [cut] > > In my mind, the whole mess looks more like a gigantic game of nuclear > whack-a-mole, and the only winning move is not to play. (The optimist > believes we are living in the best of all possible worlds. The pessimist > is

Re: [DNG] elogind testing for experimental and ascii-proposed

KatolaZ wrote on 19.01.2018 17:36: > On Fri, Jan 19, 2018 at 02:17:28PM +0100, Irrwahn wrote: >> [...], because currently one cannot >> have policykit without having consolekit installed with it, due to >> the "Depends". The package should have something akin to: >> >> Depends: libpam-elogind

Re: [DNG] elogind testing for experimental and ascii-proposed

On Fri, Jan 19, 2018 at 06:03:59PM +0100, Didier Kryn wrote: [cut] > >     I think the concept of session is still usefull in the framework of a > Desktop Environment. When you log into that kind of environment, you have a > few services associated to it which make your life easier, like

Re: [DNG] elogind testing for experimental and ascii-proposed

Le 19/01/2018 à 16:42, Irrwahn a écrit : Adam Borowski wrote on 19.01.2018 15:56: On Fri, Jan 19, 2018 at 02:17:28PM +0100, Irrwahn wrote: I think that has to be done anyway, because currently one cannot have policykit without having consolekit installed with it, due to the "Depends". The

Re: [DNG] elogind testing for experimental and ascii-proposed

On Fri, Jan 19, 2018 at 02:17:28PM +0100, Irrwahn wrote: [cut] > > Yes, that appears to be the most likely explanation. > > > Maybe we need to rebuild it with support for elogind. > > I think that has to be done anyway, because currently one cannot > have policykit without having consolekit

Re: [DNG] elogind testing for experimental and ascii-proposed

Adam Borowski wrote on 19.01.2018 15:56: > On Fri, Jan 19, 2018 at 02:17:28PM +0100, Irrwahn wrote: >> I think that has to be done anyway, because currently one cannot >> have policykit without having consolekit installed with it, due to >> the "Depends". The package should have something akin

Re: [DNG] elogind testing for experimental and ascii-proposed

On Fri, Jan 19, 2018 at 02:17:28PM +0100, Irrwahn wrote: > > It seems to me that these issues are caused by policykit, in devuan it > > doesn't support logind (obviously) so it's unable to authenticate > > user's requests. > > Yes, that appears to be the most likely explanation. > > > Maybe we

Re: [DNG] elogind testing for experimental and ascii-proposed

Hleb Valoshka wrote on 19.01.2018 13:28: > On 1/19/18, Irrwahn wrote: >> Scenario 1: >> --- >> │ PAM profiles to enable: >> │ >> │[*] Unix authentication >> │[*] Authenticate using SSH keys and start ssh-agent >> │[*] elogind Session Management >> │

Re: [DNG] elogind testing for experimental and ascii-proposed

On 1/19/18, Irrwahn wrote: > Scenario 1: > --- > │ PAM profiles to enable: > │ > │[*] Unix authentication > │[*] Authenticate using SSH keys and start ssh-agent > │[*] elogind Session Management > │[ ] ConsoleKit Session Management > > User

Re: [DNG] elogind testing for experimental and ascii-proposed

Andreas Messer wrote on 19.01.2018 07:16: > That seems strange. loginctl is a elogind command and when elogind does not > know about the session loginctl should reject or ask for auth. I'll dig into > this a little bit more. Probably time to setup a vm. So, I did a little more testing: * Fresh

Re: [DNG] elogind testing for experimental and ascii-proposed

Andreas Messer wrote on 19.01.2018 07:16: > On Wed, Jan 17, 2018 at 09:26:59PM +0100, Irrwahn wrote: >> Outcome is the same when logged in via a VT console, while elogind >> is fully enabled (and ck2 and pk installed). With elogind disabled >> (ck+pk only), no extra authentication is needed. >

Re: [DNG] elogind testing for experimental and ascii-proposed

On Wed, Jan 17, 2018 at 09:26:59PM +0100, Irrwahn wrote: > Hleb Valoshka wrote on 17.01.2018 20:54: > > [...] > > Can you repeat the same but with a local login? > > Outcome is the same when logged in via a VT console, while elogind > is fully enabled (and ck2 and pk installed). With elogind

Re: [DNG] elogind testing for experimental and ascii-proposed

Hleb Valoshka wrote on 17.01.2018 20:54: > On 1/17/18, Irrwahn wrote: > >> * screen sessions killed on logout >> (regression, works with elogind disabled!) > > This is because elogind is designed to be logind replacement (and > actually shares its code) and so it's

Re: [DNG] elogind testing for experimental and ascii-proposed

On 1/17/18, Irrwahn wrote: > * screen sessions killed on logout > (regression, works with elogind disabled!) This is because elogind is designed to be logind replacement (and actually shares its code) and so it's bug-for-bug compatible. Systemd uses cgroups to

Re: [DNG] elogind testing for experimental and ascii-proposed

Andreas Messer wrote on 16.01.2018 22:24: > since we have to test elogind now with various setups, KatolaZ asked me to > write a short guide what needs to be tested. So here we go: [snipped procedure] I gave it a quick spin on my ascii VM with lightdm and XFCE: 1. Simply installing elogind