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
On 2018-01-19 17:36, KatolaZ wrote:
BTW, GNOME will most probably not work anyway without systemd, and I
haven't seen many GNOME fans around here anyway, so GNOME has
effectively been given the heave-ho so far...
HND
KatolaZ
gnome as a desktop may be absent but gnome is very much entwined
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
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
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
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
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
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
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
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:
>>
>>
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
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
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
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
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
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
On Wed, 17 Jan 2018 13:22:13 +0300, Hleb wrote in message
:
> On 1/17/18, Andreas Messer wrote:
>
> > Btw, "ck-list-sessions" crashes for me:
> ...
>
> Have you rebooted your pc after upgrading CK to CK2?
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
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
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
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
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
>> │
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
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
24 matches
Mail list logo