So what we really need to do here is to not create CK sessions for every
system session like cron. It creates not only this bug, but has a couple
of other side effects, like making system users appear in gdm, and
showing them as "most popular login" in the gdm user list.
I discussed this with Steve Langasek, and he said that he plans to split
"common-session", so that we will get a new /etc/pam.d/common-session-
interactive. Then libpam-ck-connector could register there instead of to
common-session.
** Summary changed:
- Trying to shut down or restart falsely suggests others are logged in
+ Do not create CK sessions for cron and other system sessions
** Also affects: pam (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pam (Ubuntu)
Status: New => Triaged
--
Do not create CK sessions for cron and other system sessions
https://bugs.launchpad.net/bugs/287715
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
