Red Hat Bugzilla – Bug 572199
tty logins stays in sessions list for user switching even if user has already logged out
Last modified: 2010-09-30 02:15:02 EDT
+++ This bug was initially created as a clone of Bug #470004 +++
Description of problem:
If user switches to terminal (Ctrl+Alt+Fx) use it and then exits, this terminal stays listed in sessions to switch to
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.switch to terminal (Ctrl+Alt+F2)
2.enter username and password
"user: TTY login (vt2)" is listed even if session has been already terminated
only active sessions are listed
if you repeat above steps, you can achieve "user: TTY login (vt2)" to be listed twice (three times, four...)
--- Additional comment from email@example.com on 2008-11-05 08:55:13 EST ---
Interesting, I wonder by what method kde uses to determine users logged into tty's... either that's broken or console logins are.
"last" gives interesting results for me:
rdieter1 tty2 ... Wed nov 5 08:52 gone - no logout
except, I *did* logout.
--- Additional comment from firstname.lastname@example.org on 2008-11-07 12:45:28 EST ---
OK, looks like tty logins never finish logging out. For me, ALT-F2 goto console, login... do stuff... logout... stuck, no login: prompt
Now, who to blame for this? :)
--- Additional comment from email@example.com on 2008-11-07 12:46:45 EST ---
bouncing over to util-linux-ng (owner of login), in hopes of some insight.
--- Additional comment from firstname.lastname@example.org on 2008-11-25 12:50:35 EST ---
Interesting, I can't reproduce anymore, how about you?
--- Additional comment from email@example.com on 2008-11-25 23:48:14 EST ---
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
--- Additional comment from firstname.lastname@example.org on 2008-11-26 04:29:26 EST ---
I'm in work now, where I have kde 4.1.3 packages from updates-testing and it doesn't work for me. Still the "same" problem.
I think there is (maybe) one difference: If I try to switch user via "start"->Switch user and select tty console, it starts new session with kdm as if I select "start new session". If I try to switch via screen saver lock or via kdm, it "works" as usual. I don't know if this is new change or if it was working this way already.
I can test also on system updated without updates-testing today later if you want.
--- Additional comment from email@example.com on 2009-01-30 09:57:39 EST ---
I take back comment #4, console logins are still not registerring logout, 'last' still reports only 'gone - no logout'
--- Additional comment from firstname.lastname@example.org on 2009-03-19 09:19:46 EDT ---
It seems that /sbin/init from upstart does not care about utmp at all.
(Note that mingetty(8) and login(1) can create a new utmp entry on systems
where init(8) is broken, but init(8) has to set the entry to DEAD_PROCESS
state when user logout and login process has exited).
See utmp man page:
The first entries ever created result from init(8) processing inittab(5).
Before an entry is processed, though, init(8) cleans up utmp by setting
ut_type to DEAD_PROCESS, clearing ut_user, ut_host, and ut_time with null
bytes for each record which ut_type is not DEAD_PROCESS or RUN_LVL and where
no process with PID ut_pid exists. If no empty record with the needed ut_id
can be found, init(8) creates a new one. It sets ut_id from the inittab,
ut_pid and ut_time to the current values, and ut_type to INIT_PROCESS.
mingetty(8) (or agetty(8)) locates the entry by the PID, changes ut_type to
LOGIN_PRO- CESS, changes ut_time, sets ut_line, and waits for connection to be
established. login(1), after a user has been authenticated, changes ut_type
to USER_PROCESS, changes ut_time, and sets ut_host and ut_addr. Depending on
mingetty(8) (or agetty(8)) and login(1), records may be located by ut_line
instead of the preferable ut_pid.
When init(8) finds that a process has exited, it locates its utmp entry by
ut_pid, sets ut_type to DEAD_PROCESS, and clears ut_user, ut_host and ut_time
with null bytes.
Reassignig to upstart.
--- Additional comment from email@example.com on 2009-05-20 09:18:35 EDT ---
Created an attachment (id=344797)
It fixes problem with tty logins which stays in sessions list.
It adds new stanza - utmp - and writes utmp entries and wtmp log
as described in utmp(5).
Needs to add "utmp <id>" to /etc/event.d/tty<id>
Tested againts F10 and devel branch
--- Additional comment from firstname.lastname@example.org on 2009-05-20 10:31:55 EDT ---
I would greatly prefer to not change the job syntax if at all possible.
--- Additional comment from email@example.com on 2009-05-20 10:37:40 EDT ---
Historically /sbin/init in upstart hasn't directly altered utmp. The upstart runlevel command does the utmp editing by itself.
Following that pattern, the right way is to create a helper.
--- Additional comment from firstname.lastname@example.org on 2009-05-24 10:39:56 EDT ---
*** Bug 502362 has been marked as a duplicate of this bug. ***
--- Additional comment from email@example.com on 2009-06-04 10:12:42 EDT ---
it folows upstart 0.5 roadmap https://lists.ubuntu.com/archives/upstart-devel/2007-October/000468.html:
Finally init will maintain INIT_PROCESS and DEAD_PROCESS entries in utmp
for jobs that require it, through a "utmp id" stanza. The general user
of this will the getty job, where such utmp entries are necessary for
--- Additional comment from firstname.lastname@example.org on 2009-06-08 10:08:41 EDT ---
> Following that pattern, the right way is to create a helper.
I can't imagine how this helper should work. Do you have any idea about that?
Anyway it has to be somehow handled by init. There should be set line with INIT_PROCESS and right pid (of new process) before running new getty (or another tty process).
> I would greatly prefer to not change the job syntax if at all possible.
It's a way how to tell init what id (representing terminal name suffix) use when writes to utmp line with INIT_PROCESS before exec to getty as long as we don't use inittab for that.
--- Additional comment from email@example.com on 2009-06-17 12:16:08 EDT ---
what do you think about this:
create something called utmp-helper (compat/sysv/utmp-helper.c) with usage:
utmp-helper --id <terminal suffix> -- <command for what we need utmp handling>
utmp-helper will do fork(), in child it will save pid of new process, id and INIT_PROCESS to utmp table, call setsid() for controlling tty and execv() to <command for what we need utmp handling>, in parrent it will wait() until child terminates, then set DEAD_PROCESS into utmp table and log to wtmp log.
and then exec line in /etc/event.d/tty* will be changed to:
exec utmp-helper --id 1 -- /sbin/mingetty tty1
--- Additional comment from firstname.lastname@example.org on 2009-06-18 08:39:06 EDT ---
looks like upstream will accept patch from Comment #9
--- Additional comment from email@example.com on 2009-09-07 21:31:33 EDT ---
Has this patch made it into F10/F11/Rawhide?
Steven M. Parrish - KDE Triage Master
- PackageKit Triager
Fedora Bugzappers volunteer triage team
--- Additional comment from firstname.lastname@example.org on 2009-09-08 08:31:26 EDT ---
Afaict, the patch has not been integrated, but I'd love to be wrong.
--- Additional comment from email@example.com on 2009-10-01 11:49:22 EDT ---
Unfortunately it seems you're not wrong, the problem persists with upstart-0.3.11-1.fc11.x86_64 on F-11, and looks like later versions don't have it either.
--- Additional comment from firstname.lastname@example.org on 2009-10-01 11:49:58 EDT ---
(In reply to comment #19)
> and looks like later versions don't have it either.
...where with "it" I mean a fix.
--- Additional comment from email@example.com on 2009-10-01 13:34:41 EDT ---
Upstream is not doing any more releases for 0.3.x. Since it doesn't look like we're advancing to the next version any time soon this should probably be rolled in by us.
--- Additional comment from firstname.lastname@example.org on 2009-11-12 16:22:01 EST ---
confirmed issue remains in f12, rebasing.
--- Additional comment from email@example.com on 2009-11-30 07:56:19 EST ---
*** Bug 542138 has been marked as a duplicate of this bug. ***
--- Additional comment from firstname.lastname@example.org on 2009-12-04 10:58:33 EST ---
Created an attachment (id=376109)
add utmp_clean_id and call it from post-stop stanza
another helper suggestion:
call umtp_clean_id in post-stop stanza, eg for /etc/event.d/tty2:
post-stop exec /sbin/utmp_clean_id 2
utmp_clean_id is simple utility which cleans (sets type to DEAD_PROCESS and nulls other rows) lines with given id and type LOGIN_PROCESS or USER_PROCESS.
these patch is related to initscripts that provides /etc/event.d/tty*
--- Additional comment from email@example.com on 2009-12-04 11:34:40 EST ---
http://koji.fedoraproject.org/koji/taskinfo?taskID=1849861 scratch build
--- Additional comment from firstname.lastname@example.org on 2010-03-09 08:54:20 EST ---
Created an attachment (id=398797)
set DEAD_PROCESS for died proccess with pid in utmp table
(with this patch) init tries to find utmp entry for each tracked process which died. If entry is found, it sets type to DEAD_PROCESS and logs to wtmp log.
mingetty takes care about setting INIT_PROCESS/LOGIN_PROCESS itself.
There is no need to change anything else like it was in previous patches.
koji scratch build is here http://koji.fedoraproject.org/koji/taskinfo?taskID=2041266
--- Additional comment from email@example.com on 2010-03-10 06:50:04 EST ---
upstart-0.3.11-4.fc12 has been submitted as an update for Fedora 12.
Confirmed bug present again after upgrading to f13. :(
Created attachment 409105 [details]
set DEAD_PROCESS for died proccess with pid in utmp table
If we assume that *getty takes care about setting INIT_PROCESS/LOGIN_PROCESS itself, we need just set DEAD_PROCESS for dead processes with pid in utmp table and log it into wtmp.
Init goes through the utmp table, tries to find entry with dead process pid and sets it to DEAD_PROCESS.
Scratch build , sent to upstream 
upstart-0.6.5-6.fc13 has been submitted as an update for Fedora 13.
upstart-0.6.5-9.fc14 has been submitted as an update for Fedora 14.
upstart-0.6.5-9.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update upstart'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/upstart-0.6.5-9.fc14
upstart-0.6.5-6.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
upstart-0.6.5-9.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.