Hide Forgot
Here's a fun one to try. Create a new user. Log in as that user via kdm. Log out. 'finger'. Here's what I get, for two users I made up: Login Name Tty Idle fred *pts/0 25d jim *pts/0 25d Does anyone else get this?
Actually, it doesn't seem to happen from kdm, only with startx.
This defect is considered MUST-FIX for Florence Release-Candidate #1
Okay, the smoking gun is here, in kdebase/konsole/src/kwrited.C:57: //FIXME: make sure we properly remove the utmp stamp on session end or kill
kwrited is getting killed by SIGHUP as soon as I log out.
*** Bug 25232 has been marked as a duplicate of this bug. ***
I can't figure this out. After logging in, kwrited has a child, cat. kwrited is in the same process group and session as all the other kdeinit:* processes, and cat is in its own process group, and its own session. Only cat has a controlling terminal. Yet they _both_ get a SIGHUP, when I can only see one being sent. Am I looking in the wrong place? Also, althought TEPty::TEPty does: connect(this, SIGNAL(processExited(KProcess *)), this, SLOT(donePty())); donePty never gets called. :-(
I've reported this in the KDE bug database.
Stephan Kulow's patch does not fix the problem. For reference, this is KDE bug #19649.
Fixed in 2.0.20010204-1
Bero, are you sure? The patch you sent me didn't work entirely.
I've built a new one that works for me so far. Seems some **** thought we don't need to chownpty() if we have a /dev/ptmx device for some reason, commenting out that line fixes it (for me). Besides the patch I've sent you earlier fixes the utmp issue which is the worse part (and reasoning for the RC-1-MUSTFIX state ;) ) of the problem. If the other problem remains for you, please open a new bug rather than reopening this one.
I thought the worse part was the device permissions one (#25232). I'll reopen it, since it seems to be a separate (kdm) thing.