Public bug reported: Binary package hint: timeoutd
The timeout daemon seems to kill itself after partially-succesful session timeout action... - firstly, it does not display x-window popups (any!) - messages are echoed under console screen (virtual terminal next to that used/reserved by gdm); - after all (after the 'last' beep, when timeout limit is reached) it crashes user's session - does not logging out but just restarts (?) gdm - command 'last -10' says that user is still logged; - timeoutd still tries to logout user XYZ (10 or more times with beep; from '/var/log/syslogd'): (...) timeoutd[12168]: User XYZ exceeded maximum daily limit (on for 486 minutes, max=180). (...) timeoutd[12168]: chk_ssh(): PID 11929 does not exist. Something went wrong. Ignoring. After that it finishes his work ('ps -A|grep timeoutd' says nothing). Now, the user XYZ is able to log in without any time restrictions... Timeoutd process can be 'saved': another user should log in before last beep occurs. +=+=+=+=+ Ubuntu - v7.10 (Gutsy - dist-upgraded from Feisty) with all updates timeoutd - v1.5-10 gdm - v2.20.1-0ubuntu1 ** Affects: timeoutd (Ubuntu) Importance: Undecided Status: New -- timeoutd crashes after session 'break' https://bugs.launchpad.net/bugs/165254 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs