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.
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.