[Pkg-systemd-maintainers] gdm3: GLib.js still an issue GDM doesn't get to greeter

[Emilio Pozuelo Monfort]

On 17/11/13 16:49, Les Schaffer wrote:
> On 11/17/2013 07:09 AM, Emilio Pozuelo Monfort wrote:
>> Can you strace logind, then try to start gdm, and send the strace
>> output? That could help in determining where this error is coming
>> from. Thanks, Emilio 
> 
> ok. i:
> 
> 1. killed kdm
> 2. strace -p 4715 -o logind-strace &
> 3. service gdm3 start
> 4. copied logind-strace after gdm3 failure to greet, and killed strace

Thanks! I think the relevant part is:

open("/proc/8417/cgroup", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
sendmsg(9, {msg_name(0)=NULL,
msg_iov(2)=[{"l\3\1\1\24\0\0\0+\0\0\0W\0\0\0\6\1s\0\5\0\0\0:1.78\0\0\0"...,
104}, {"\17\0\0\0No such process\0", 20}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 124

What's happening here is:

libpam-systemd sends its own pid (8417) in the CreateSession dbus message.
logind looks for /proc/8417/cgroup which doesn't exist, so it thinks there's
no pid 8417 running, and returns ESRCH. However /proc/8417 has to be there as
getpid() in libpam-systemd won't fail and I doubt there's a problem in the dbus
message passing. So if I'm right, the problem has to be that the cgroup files
are missing.

I see you're running linux 3.12. Where have you got it from? Have you built it
yourself? Was CONFIG_CGROUPS disabled when building it? Do other
/proc/$pid/cgroup files exist?

Cheers,
Emilio