Comment 19 for bug 445953

> There's nothing incorrect about having a PAM session, many things run as different users have PAM sessions (e.g. cron scripts!)

> They're non-interactive sessions, so should not be registered as a "logged in user" - the bug here is with CK for treating
> all active sessions as *inter*active sessions

cron scripts, however, no longer produce this error, because they now reference /etc/pam.d/common-session-noninteractive which doesn't call pam_ck_connector. The reason mythtv is still having this problem is that it calls su, and su must (and does) also support interactive sessions, so it *does* invoke pam_ck_connector unconditionally (su has no distinction between interactive vs. noninteractive uses).

Does mythtv *rely* on consolekit sessions in any way? (Or on any other aspects of PAM session handling?) If not, I think the easier fix here is to have mythtv not call su to change UIDs - this is run from an init script, it's a system service, it could just as well use start-stop-daemon for this and bypass PAM entirely.