Hi,
I've run into a problem after the latest udev update.
Is GDM just supposed to use only PAM config[1] to register with
systemd-logind? If so, it's either broken or I've ballsed something up
(more than likely!)
The problem I'm getting is thus:
With udev 172, udev-acl would apply ACLs to
On Sat, 27.08.11 13:02, Colin Guthrie (gm...@colin.guthr.ie) wrote:
Hi,
I've run into a problem after the latest udev update.
Is GDM just supposed to use only PAM config[1] to register with
systemd-logind? If so, it's either broken or I've ballsed something up
(more than likely!)
You
'Twas brillig, and Lennart Poettering at 27/08/11 13:53 did gyre and gimble:
On Sat, 27.08.11 13:02, Colin Guthrie (gm...@colin.guthr.ie) wrote:
Hi,
I've run into a problem after the latest udev update.
Is GDM just supposed to use only PAM config[1] to register with
systemd-logind? If so,
'Twas brillig, and Colin Guthrie at 27/08/11 13:59 did gyre and gimble:
'Twas brillig, and Lennart Poettering at 27/08/11 13:53 did gyre and gimble:
On Sat, 27.08.11 13:02, Colin Guthrie (gm...@colin.guthr.ie) wrote:
Hi,
I've run into a problem after the latest udev update.
Is GDM just
