Description of problem: Seeing the following occassionally: kdm: :0[21888]: pam_timestamp(kdm:auth): timestamp file `/var/run/sudo/root/:0:vasha' is older than oldest login, disallowing access to kdm for user root kdm: :0[21888]: pam_timestamp(kdm:session): updated timestamp file `/var/run/sudo/root/:0:vasha' kdm: :0[21888]: pam_selinux(kdm:session): Warning! Could not get current context for /dev/:0, not relabeling: No such file or directory Version-Release number of selected component (if applicable): kdebase-3.5.1-5 Also see pam_timestamp messages on up to date FC4: kdm: :0[21986]: pam_timestamp: timestamp file `/var/run/sudo/root/:0:mfw' has unacceptable age (175195 seconds), disallowing access to kdm for user root kdm: :0[501]: pam_timestamp: timestamp file `/var/run/sudo/root/:0:herten' is older than oldest login, disallowing access to kdm for user root Just wondering if this is a problem or not. Logwatch reports them as Unmatched Entries.
Reassigning to pam.
The pam_timestamp entries are fully legitimate information messages. However they don't mean there is a problem (so they could be probably ignored in logwatch). The pam_selinux message probably shouldn't be reported as this is not something you could/should fix.