On Wed, 30 Aug 2017 19:06:46 +0200 "Cliff McDiarmid" <[email protected]> wrote:
> and no, PAM it would seem isn't to blame. Still getting messages about > logind and PAM(see attached log). Cliff, It could be a PAM setup issue: https://ubuntuforums.org/archive/index.php/t-2230602.html (last post) Also, are you using hidepid=2 in the mounting of /proc (within /etc/fstab)? https://bugs.archlinux.org/task/31814 "Well after hours of debugging and just trying random things I could think of, I straced gdm... And wading through the megabytes of noise was worthwhile, I found this critical line: [pid 2063] open("/proc/1/cgroup", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) I'm mounting /proc with options hidepid=2 -- which hides other users' processes. It never caused me a problem so far. But apparently Gnome 3.6 relies on poking around in the details of the init process." and also: https://unix.stackexchange.com/questions/370597/is-systemds-logind-or-gnome-wayland-session-incompatible-with-hidepid-2/370607 Cheers, Mike -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
