Description of problem: Version-Release number of selected component (if applicable): XFree86-4.2.0-8 (which I guess is the right component, since it contains sessreg) gdm-2.2.3.1-22 How reproducible: Always. Steps to Reproduce: 1.Log in with gdm 2.Run "last" Actual results: It says uname :0 Thu Jan 16 17:05 gone - no logout even though I'm still logged in. Expected results: I expected "still logged in" as I get when I login from a console.
Now I think the problem is in gdm. last says "no logout" because the ut_pid process in wtmp doesn't exist any longer. sessreg puts the parent process in ut_pid which won't be the right process when sessreg is done in /etc/X11/gdm/PreSession/Default.
Adding GNOME guys to CC for comment.
You can't NEEDINFO unless you ask a question. ;-) I would have to investigate, same as anyone else. I'll cc more people in case they have ideas but basically we have to debug the problem.
Ok, reassigning to gdm for now as it seems more of a gdm issue from the above info.
This is a problem in the /etc/X11/gdm/PreSession/Default file. Make sure that the line that runs sessreg has an exec in it. As far as I can see this is fixed in rh8. Also the default script in the distro fixes this.
Ah, this is reported for 7.3. Should be fixed in 8.