-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-03-06 at 19:04 +0100, Michael Biebl wrote:
> This is usually not a good idea, as apt will pick a package at random if
> none is installed yet. You should always list a real package or
> default-logind first.
I've already changed that fo
On Fri, 22 Feb 2019 13:59:53 + Mark Hindley wrote:
> Thanks.
>
> A further suggestion, now systemd 241-1 has been uploaded to unstable with
> libpam-systemd which provides logind (closing #915407), the dependencies could
> be simplified to
>
> logind [linux-any] | consolekit,
This is usual
On Mon, Feb 25, 2019 at 01:25:00PM +0100, Yves-Alexis Perez wrote:
> > My point was that it's a bit late to just have “works for me” and I'd rather
> > have some pam-experts help on this.
Yes, I agree. I was just offering the best I can :)
> Also something to remember is that it's the pam configu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-02-25 at 13:13 +0100, Yves-Alexis Perez wrote:
> On Sat, 2019-02-23 at 16:44 +, Mark Hindley wrote:
> > On Sat, Feb 23, 2019 at 02:13:22PM +0100, Yves-Alexis Perez wrote:
> > > For the pam configuration, yes I didn't change anything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-02-23 at 16:44 +, Mark Hindley wrote:
> On Sat, Feb 23, 2019 at 02:13:22PM +0100, Yves-Alexis Perez wrote:
> > For the pam configuration, yes I didn't change anything because I honestly
> > don't know enough about it and I'm not real
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-02-25 at 11:53 +, Mark Hindley wrote:
> Yes, or even use the new default-logind virtual package (currently provided by
> libpam-systemd) as well:
>
> default-logind [linux-any] | logind [linux-any]
That won't fix the issue that th
On Sat, Feb 23, 2019 at 02:13:22PM +0100, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Fri, 2019-02-22 at 18:34 +0100, Ansgar wrote:
> > On Fri, 2019-02-22 at 13:59 +, Mark Hindley wrote:
> > > A further suggestion, now systemd 241-1 has been uploaded to
On Sat, Feb 23, 2019 at 02:13:22PM +0100, Yves-Alexis Perez wrote:
> For the pam configuration, yes I didn't change anything because I honestly
> don't know enough about it and I'm not really inclined to do potentially
> invasive stuff just during the freeze. So any help appreciated here.
I wouldn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-02-22 at 18:34 +0100, Ansgar wrote:
> On Fri, 2019-02-22 at 13:59 +, Mark Hindley wrote:
> > A further suggestion, now systemd 241-1 has been uploaded to unstable
> > with
> > libpam-systemd which provides logind (closing #915407), t
On Fri, Feb 22, 2019 at 07:17:55PM +0100, Ansgar wrote:
> > > So the PAM configuration is no longer relevant?
> >
> > Yes, I think the PAM configuration change is still required.
>
> So the logind dependency is still wrong as a different logind provider
> than those listed in the PAM configuratio
On Fri, 2019-02-22 at 17:46 +, Mark Hindley wrote:
> On Fri, Feb 22, 2019 at 06:34:09PM +0100, Ansgar wrote:
> > On Fri, 2019-02-22 at 13:59 +, Mark Hindley wrote:
> > > A further suggestion, now systemd 241-1 has been uploaded to
> > > unstable
> > > with
> > > libpam-systemd which provide
On Fri, Feb 22, 2019 at 06:34:09PM +0100, Ansgar wrote:
> On Fri, 2019-02-22 at 13:59 +, Mark Hindley wrote:
> > A further suggestion, now systemd 241-1 has been uploaded to unstable
> > with
> > libpam-systemd which provides logind (closing #915407), the
> > dependencies could
> > be simplifie
On Fri, 2019-02-22 at 13:59 +, Mark Hindley wrote:
> A further suggestion, now systemd 241-1 has been uploaded to unstable
> with
> libpam-systemd which provides logind (closing #915407), the
> dependencies could
> be simplified to
>
> logind [linux-any] | consolekit,
So the PAM configuratio
Thanks.
A further suggestion, now systemd 241-1 has been uploaded to unstable with
libpam-systemd which provides logind (closing #915407), the dependencies could
be simplified to
logind [linux-any] | consolekit,
Mark
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-02-12 at 20:05 +, Mark Hindley wrote:
> As /etc/pam.d/lightdm-greeter doesn't source common-session (should it?), the
> extra line is required.
To be honest, I'm definitely not a PAM expert, so maybe it would be better to
do it like
On Tue, Feb 12, 2019 at 08:27:40PM +0100, Ansgar wrote:
> Mark Hindley writes:
> > diff --git a/debian/control b/debian/control
> > index fff913a..88aebb8 100644
> > --- a/debian/control
> > +++ b/debian/control
> > @@ -33,7 +33,7 @@ Package: lightdm
> > Architecture: any
> > Depends: adduser,
>
Mark Hindley writes:
> diff --git a/debian/control b/debian/control
> index fff913a..88aebb8 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -33,7 +33,7 @@ Package: lightdm
> Architecture: any
> Depends: adduser,
> dbus,
> - libpam-systemd [linux-any] | consolekit,
> +
Package: lightdm
Severity: important
Tags: patch
Dear Maintainer,
Please add support for elogind so that lightdm can be used with non-systemd
inits.
The virtual package logind has been seconded for inclusion in Debian Policy (see
#917431) and elogind providing this has migrated to testing.
For
18 matches
Mail list logo
