Bug 82034 - gone - no logout
gone - no logout
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: gdm (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-16 11:55 EST by Per Starbäck
Modified: 2007-04-18 12:50 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-03 14:59:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Per Starbäck 2003-01-16 11:55:31 EST
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.
Comment 1 Per Starbäck 2003-01-22 13:43:07 EST
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.
Comment 2 Mike A. Harris 2003-01-24 01:08:54 EST
Adding GNOME guys to CC for comment.
Comment 3 Havoc Pennington 2003-01-24 01:29:48 EST
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.
Comment 4 Mike A. Harris 2003-01-24 02:06:21 EST
Ok, reassigning to gdm for now as it seems more of a gdm issue from
the above info.
Comment 5 George Lebl 2003-01-24 12:03:31 EST
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.
Comment 6 Havoc Pennington 2003-02-03 14:59:41 EST
Ah, this is reported for 7.3. Should be fixed in 8.

Note You need to log in before you can comment on or make changes to this bug.