[Bug 165254] [NEW] timeoutd crashes after session 'break'

Launchpad Bug Tracker 165254 at bugs.launchpad.net
Mon Jun 1 04:05:49 BST 2009


You have been subscribed to a public bug by Matt Trudel (mathieu-tl):

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
     Assignee: Shawn Willden (shawn-ubuntu-willden)
         Status: Confirmed

-- 
timeoutd crashes after session 'break'
https://bugs.edge.launchpad.net/bugs/165254
You received this bug notification because you are a member of Ubuntu Sponsors for universe, which is a direct subscriber.



More information about the Ubuntu-universe-sponsors mailing list