Bug 1391156

Summary: who command returns unknown user
Product: Red Hat Enterprise Linux 7 Reporter: Chinmay Paradkar <cparadka>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: jaeshin, mboisver, mclasen, tpelka, xingli
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: gdm-3.26.1-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 12:55:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1420851, 1479818    

Description Chinmay Paradkar 2016-11-02 16:23:25 UTC 
Description of problem:
The "unknown" user in who and last command appears when running in graphical.target mode. It does not appear when running in multi-user.target mode

Version-Release number of selected component (if applicable):
gdm-3.14.2-12.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. ssh in when no user is logged into the console
2. run 'who -u'
3. run last 

Actual results:
# who -u
(unknown) :0           2016-11-01 15:28   ?          1710 (:0)
root     pts/0        2016-11-02 21:48   .         15132 (10.76.0.219)

Expected results:
# who -u
root     pts/0        2016-11-02 21:48   .         15132 (10.76.0.219)

Additional info:
Upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=760834

Code is here:
-------------
        if (user_name != NULL) {•
                username = user_name;•
        } else {•
                username = "(unknown)";•
        }•
-------------
Comment 5 Michael Boisvert 2018-01-04 18:07:49 UTC 
I could not find an unknown user in 3.26.
Comment 8 errata-xmlrpc 2018-04-10 12:55:16 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0770