From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
Description of problem:
I get different results when using 'who' and 'w' command on Fedora
C1. 'w' seems to work ok, but 'who' displays extra users which are
allready logged out. last -f /var/run/utmp shows just a few lines,
root pts/2 somehost. Fri Nov 14 16:02 gone - no logout
root pts/2 localhost:10.0 Mon Nov 17 19:28 - 16:02 (-3+-
It seems that I get these leftovers just by opening extra 'xterm'
windows and closing it by Ctrl-D. 'who' shows the above entries as
logged in users.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. Ctrl-D to close the new window
Actual Results: who shows the previous pts and user as logged on.
Expected Results: exited user should not be shown as logged on
Nothing to do with who, but with xterm.
Should this bug be reopened for xterm?
I guess 'who' could still parse "gone - no logout" as 'gone'
Anyway, doing the same from windows logging in with ssh (Tera Term)
and immediately logging out with Ctrl-D:
#last -f /var/run/utmp
root pts/1 hostname Wed Dec 3 15:37 gone - no logout
root pts/1 Dec 3 15:37 (hostname)
twaugh) How is this an xterm bug exactly?
Maintenance of utmp is nothing to do with 'who'.
I was thinking of interpretation of contents of utmp rather than
creation of the entries there. I'll have to examine SuSv3 to see
if it specifies the valid entries for utmp.
Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue. Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:
If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.
I am currently using FC2 with all available errata/updates. I still
see this issue.
I get these entries from logins from other hosts with ssh and plain
text shell (i.e. no xterm). So I assume this error is related to
bash/ssh(d)/who or whoever updateds the utmp.
Seems to work on FC3