Version: 3.5.6-0ubuntu13 (using KDE KDE 3.5.6) Installed from: Ubuntu Packages OS: Linux After logging into and out of a terminal session (a TTY login vt[1-4]) the user still seems to be logged in when you go to the "Switch users" menu. This bug was originally reported in Malone - Ubuntu's bug tracker and can be viewed at https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/73025 by Albert Bogdanowicz. I have also reproduced this bug and can provide any additional information if required.
please run "who -a" before, during and after somebody is logged in on tty* the first time. post the first complete and "diff -u" first->second and second->third. note: start as few terminals as possible before you do it.
Here is the additional information you requested: bdmurray@flash:~/tmp$ who -a | tee first.log system boot 2007-03-01 16:00 run-level 2 2007-03-01 16:00 last= LOGIN tty5 2007-03-01 16:00 5175 id=5 LOGIN tty4 2007-03-01 16:00 5174 id=4 LOGIN tty3 2007-03-01 16:00 5178 id=3 LOGIN tty6 2007-03-01 16:00 5180 id=6 bdmurray ? :0 2007-03-06 07:14 ? 9975 :1 2007-03-06 15:24 0 id=:1 term=0 exit=0 :2 2007-03-01 20:15 0 id=:2 term=0 exit=0 LOGIN tty2 2007-03-01 21:17 27591 id=2 bdmurray + pts/13 2007-03-02 18:32 00:03 15337 (:pts/8:S.0) pts/18 2007-03-04 08:25 7268 id=s/18 term=0 exit=0 pts/18 2007-03-04 23:11 24236 id=/18 term=0 exit=0 LOGIN tty1 2007-03-06 15:22 13929 id=1 bdmurray@flash:~/tmp$ diff -u first.log during.log --- first.log 2007-03-06 15:24:32.000000000 -0800 +++ during.log 2007-03-06 15:25:12.000000000 -0800 @@ -3,12 +3,13 @@ LOGIN tty5 2007-03-01 16:00 5175 id=5 LOGIN tty4 2007-03-01 16:00 5174 id=4 LOGIN tty3 2007-03-01 16:00 5178 id=3 +bdmurray - tty1 2007-03-06 15:25 . 13929 LOGIN tty6 2007-03-01 16:00 5180 id=6 bdmurray ? :0 2007-03-06 07:14 ? 9975 :1 2007-03-06 15:24 0 id=:1 term=0 exit=0 :2 2007-03-01 20:15 0 id=:2 term=0 exit=0 LOGIN tty2 2007-03-01 21:17 27591 id=2 -bdmurray + pts/13 2007-03-02 18:32 00:03 15337 (:pts/8:S.0) +bdmurray + pts/13 2007-03-02 18:32 00:04 15337 (:pts/8:S.0) pts/18 2007-03-04 08:25 7268 id=s/18 term=0 exit=0 pts/18 2007-03-04 23:11 24236 id=/18 term=0 exit=0 LOGIN tty1 2007-03-06 15:22 13929 id=1 bdmurray@flash:~/tmp$ diff -u during.log after.log --- during.log 2007-03-06 15:25:12.000000000 -0800 +++ after.log 2007-03-06 15:25:48.000000000 -0800 @@ -3,7 +3,6 @@ LOGIN tty5 2007-03-01 16:00 5175 id=5 LOGIN tty4 2007-03-01 16:00 5174 id=4 LOGIN tty3 2007-03-01 16:00 5178 id=3 -bdmurray - tty1 2007-03-06 15:25 . 13929 LOGIN tty6 2007-03-01 16:00 5180 id=6 bdmurray ? :0 2007-03-06 07:14 ? 9975 :1 2007-03-06 15:24 0 id=:1 term=0 exit=0 @@ -12,4 +11,4 @@ bdmurray + pts/13 2007-03-02 18:32 00:04 15337 (:pts/8:S.0) pts/18 2007-03-04 08:25 7268 id=s/18 term=0 exit=0 pts/18 2007-03-04 23:11 24236 id=/18 term=0 exit=0 -LOGIN tty1 2007-03-06 15:22 13929 id=1 +LOGIN tty1 2007-03-06 15:25 13995 id=1 Please let me know if you need anything else.
uhm ... just to make sure: the first one is from before you could see the problem, yes? the uptime doesn't exactly suggest this. anyway, there seem to be no dead entries left behind, unless who applies a different interpretation than kdm. try ssh localhost. that login should also appear in who output and in the shutdown warning list. and it should disappear after logout, of course. are you aware of ubuntu-/debian-specific kdm-patches to the kdm backend?
Here is the information you requested again after rebooting so the first log should be clean i.e. before any user had logged in on tty[1-4]. bdmurray@flash:~/tmp$ cat first.log system boot 2007-03-07 07:07 run-level 2 2007-03-07 07:07 last= LOGIN tty4 2007-03-07 07:07 10707 id=4 LOGIN tty2 2007-03-07 07:07 10710 id=2 LOGIN tty5 2007-03-07 07:07 10708 id=5 LOGIN tty1 2007-03-07 07:07 10712 id=1 LOGIN tty6 2007-03-07 07:07 10713 id=6 LOGIN tty3 2007-03-07 07:07 10711 id=3 bdmurray ? :0 2007-03-07 07:07 ? 12117 bdmurray + pts/17 2007-03-07 07:18 . 12770 (:pts/4:S.0) bdmurray + pts/18 2007-03-07 07:18 00:32 12775 (:pts/4:S.1) bdmurray@flash:~/tmp$ diff -u first.log during.log --- first.log 2007-03-07 07:52:09.000000000 -0800 +++ during.log 2007-03-07 07:54:46.000000000 -0800 @@ -1,11 +1,11 @@ system boot 2007-03-07 07:07 run-level 2 2007-03-07 07:07 last= LOGIN tty4 2007-03-07 07:07 10707 id=4 -LOGIN tty2 2007-03-07 07:07 10710 id=2 +bdmurray - tty2 2007-03-07 07:54 . 10710 LOGIN tty5 2007-03-07 07:07 10708 id=5 LOGIN tty1 2007-03-07 07:07 10712 id=1 LOGIN tty6 2007-03-07 07:07 10713 id=6 LOGIN tty3 2007-03-07 07:07 10711 id=3 bdmurray ? :0 2007-03-07 07:07 ? 12117 -bdmurray + pts/17 2007-03-07 07:18 . 12770 (:pts/4:S.0) -bdmurray + pts/18 2007-03-07 07:18 00:32 12775 (:pts/4:S.1) +bdmurray + pts/17 2007-03-07 07:18 00:03 12770 (:pts/4:S.0) +bdmurray + pts/18 2007-03-07 07:18 00:35 12775 (:pts/4:S.1) bdmurray@flash:~/tmp$ diff -u during.log after.log --- during.log 2007-03-07 07:54:46.000000000 -0800 +++ after.log 2007-03-07 07:55:12.000000000 -0800 @@ -1,11 +1,11 @@ system boot 2007-03-07 07:07 run-level 2 2007-03-07 07:07 last= LOGIN tty4 2007-03-07 07:07 10707 id=4 -bdmurray - tty2 2007-03-07 07:54 . 10710 LOGIN tty5 2007-03-07 07:07 10708 id=5 LOGIN tty1 2007-03-07 07:07 10712 id=1 LOGIN tty6 2007-03-07 07:07 10713 id=6 LOGIN tty3 2007-03-07 07:07 10711 id=3 bdmurray ? :0 2007-03-07 07:07 ? 12117 bdmurray + pts/17 2007-03-07 07:18 00:03 12770 (:pts/4:S.0) -bdmurray + pts/18 2007-03-07 07:18 00:35 12775 (:pts/4:S.1) +bdmurray + pts/18 2007-03-07 07:18 00:36 12775 (:pts/4:S.1) +LOGIN tty2 2007-03-07 07:54 13062 id=2
nothing unusual about it ... is there a difference between 1) tty login - show kdm session list - tty logout - show kdm session list and 2) tty login - tty logout - show kdm session list ?
ping!
based on the fact that i got no new information and it just works for me, i am forced to close this.
In regards to Comment #5 - No there is not a difference between the two things. I also do not know of any ubuntu or debian specific patches to kdm. I am also able to reproduce this using kdm version 3.5.7-1ubuntu8. What other steps could I take to help troubleshoot this?
i assume you did the tests immediately after a reboot, as usual. i have no idea what else i could request from you save investigating this yourself in gdb - i could provide some assistance, but you need to know what you're doing ...
*** Bug 162715 has been marked as a duplicate of this bug. ***
Reopening, i can reproduce it on: KUbuntu 9.04 with binary packages of KDE 4.2.3 KUbuntu 9.04 with self compiled KDE trunk Fedora 10 with binary packages of KDE 4.2.2 kdmctl list shows that after login in and login out in a virtual terminal there are no changes and kcm thinks we are still logged in.
(by now) known upstart bug. https://bugs.edge.launchpad.net/upstart/+bug/183729 https://bugzilla.redhat.com/show_bug.cgi?id=470004
*** Bug 226641 has been marked as a duplicate of this bug. ***