Comment 18 for bug 395281

It's far from uncommon to use su in startup scripts - even ones crafted by local sysadmins. I don't think defining 'su' to start a CK session is the right thing to do.

Case in point: I crafted a local upstart job to run a java rmiregistry on my machine, and I su-ed it because it has no need to run as root, and no user-changing capability of its own. Later, I started getting spurious "there is another user logged in" warnings when shutting down my computer. It took some considerable head-scratching before I realized the non-obvious linkage here, and then only because I had some small prior experience with CK oddities.