Bug 28403 - last shows strange "logout" for active login
Summary: last shows strange "logout" for active login
Status: RESOLVED DUPLICATE of bug 27022
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-22 09:23 CET by w unruh
Modified: 2021-02-22 20:00 CET (History)
1 user (show)

See Also:
Source RPM: uril-linux-2.33.2
CVE:
Status comment:


Attachments

Description w unruh 2021-02-22 09:23:05 CET
last is showing strange behaviour for current login. Here is an output of last

unruh    pts/1        ::1              Mon Feb 22 08:13    gone - no logout
unruh    pts/1        ::1              Mon Feb 22 08:10 - 08:12  (00:01)
unruh    pts/1        ::1              Mon Feb 22 06:21 - 06:26  (00:04)
wtmp begins Sun Feb 21 18:32:11 2021

But that first entry is the current login, and it is certainly not gone. It is what
ran last.
I got the same behaviour for that second login when I ran last in it. 

It seems to be reporting "gone" when it should be reporting something like "current" or "still active"  or as on another machine (with the same version of last and util-linux)
unruh    pts/2        :0.0             Mon Feb 22 00:09   still logged in
Comment 1 Lewis Smith 2021-02-22 20:00:54 CET
I see the same sort of thing on Mageia 8:
 $ last
lewis    tty1         :0               Mon Feb 22 18:45   still logged in
lewis    :0                            Mon Feb 22 18:45   still logged in
lewis    console      :0               Mon Feb 22 18:45    gone - no logout
reboot   system boot  5.10.16-desktop- Mon Feb 22 18:44   still running

This rang a bell, and turns out to be a repetition of your previous bug 27022.
So I am marking this a duplicate of that, and re-opening the original one.

*** This bug has been marked as a duplicate of bug 27022 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED
CC: (none) => lewyssmith


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