Description of problem: The who command (with no args or -u) returns the following first item when no user is logged in via the console: (unknown) tty1 2011-12-05 22:56 23:10 2309 (:0) Users logged in via ssh follow. Additionally, the --count command returns 1 plus the number of logged in users. If a user is logged in via the console the first entry properly reflects that. In other words, the first entry returned by who is always tty1 (:0) regardless of whether a user is logged into the console or not. The who command from FC15 did not produce that entry when no user was logged into the console. The behavior of 'who' now differs from the behavior of 'w'. Version-Release number of selected component (if applicable): 8.12 How reproducible: Every time Steps to Reproduce: 1. ssh in when no user is logged into the console 2. run 'who -u' 3. run 'who --count' Actual results: who -u 22:14:00 up 23:18, 2 users, load average: 0.16, 0.21, 0.16 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT (unknown) tty1 2011-12-05 22:56 23:10 2309 (:0) xxxxxxx pts/0 2011-12-06 11:28 (xxxx.xxxx.com) who --count (unknown) xxxxxxxx # users=2 Expected results: who -u 22:14:00 up 23:18, 2 users, load average: 0.16, 0.21, 0.16 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT xxxxxxx pts/0 2011-12-06 11:28 (xxxx.xxxx.com) who --count xxxxxxxx # users=1 Additional info:
The 'who' utility uses getutent(), which reads the content of /var/run/utmp. The reason why the 'w' utility does not print the outstanding line is that it hides all entries that cannot by matched with an entry in /proc: best = getproc(u, tty + 5, &jcpu, &ut_pid_found); /* just skip if stale utmp entry (i.e. login proc doesn't exist). If there * is a desire a cmdline flag could be added to optionally show it with a * prefix of (stale) in front of cmd or something like that. */ if (!ut_pid_found) return; As there is nothing wrong at first glance in coreutils, I am switching the component to initscripts, which owns /var/run/utmp.
Moving to systemd for now - the issue is something wrote a bad utmp entry. Nothing in initscripts actually modifies utmp.
(In reply to comment #0) > (unknown) tty1 2011-12-05 22:56 23:10 2309 (:0) Is the gdm login screen running there? Does this line go away if you boot into multi-user.target instead of graphical.target?
Yes, the gdm login screen is running. Yes, the '(unknown)' line does go away when I switch to multi-user.target. I installed F16 on another machine and it too shows the '(unknown)' entry. Both of these machines were upgraded from F15.
gdm itself writes the '(unknown)' utmp entry. Reassigning.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This is on F17 x32 . # last | grep unknown (unknown :0 :0 Tue Jun 11 19:10 - 19:11 (00:00) (unknown :0 :0 Tue Jun 11 22:10 - 19:10 (-2:-59) (unknown :0 :0 Tue Jun 11 19:01 - down (00:00) (unknown :0 :0 Tue Jun 11 15:29 - 15:29 (00:00) ... Unfortunately i can not change the status of the bug report. Also, today the computer could not be shutted down because "another user is logged in". Sounds like a knonw f18 bug. Maybe same fix can be applied?
Reopening bug
Running last | grep unknown | wc -l on F18 164 GDM should identify itself
Same to me in Fedora 19 logged-in through ssh. $ cat /etc/fedora-release Fedora release 19 (Schrödinger’s Cat) $ who (unknown) :0 2013-06-28 22:29 (:0) easior pts/0 2013-07-02 06:13 (x.x.x.x) how to fix it?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
In Fedora 21 this issue stills occurs. Also the 'last' command return this unknown user. Version (kernel) fedora uname -a: Linux d3.17.7-300.fc21.x86_64 #1 SMP Wed Dec 17 03:08:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Additional info: This user appears in the output of the 'last' command after a reboot.
Sorry for spamming. Found this topic about my issue: http://unix.stackexchange.com/questions/118576/unknown-entries-in-kali-linux-wtmp-log-file I think its safe to ignore this user
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.