Since the revision 4f88228f upstream ck-collect-session-info does not emmit is-local parameter and sessions started with ck-launch-session (in my case in .xsessionrc) are not on Seat1 so all the local stuff (mounting removable to name one) does not work anymore. The upstream bug that that the offending patch has been created for https://bugs.freedesktop.org/show_bug.cgi?id=28377 Reproducible: Always Steps to Reproduce:
That upstream patch should be useless as the problem is in pambase, not in consolekit. See bug 342345, it should solve this one too.
(In reply to comment #1) > That upstream patch should be useless as the problem is in pambase, not in > consolekit. See bug 342345, it should solve this one too. > What I meant to say was "That upstream bug should be useless", sorry.
*** This bug has been marked as a duplicate of bug 342345 ***
so what is the workaround for xdm until bug 342345 gets some resolution? switch login managers? to what? i'd like something DE-independent, would slim work?
(In reply to comment #4) > so what is the workaround for xdm until bug 342345 gets some resolution? switch > login managers? to what? i'd like something DE-independent, would slim work? You can get the outcome of future solution of bug 342345 simply by removing the "nox11" parameter from /etc/pam.d/system-login from the pam_ck_connector.so line And then you need to propably add ck-launch-session to your desktops launch file in /etc/X11/Sessions/ for example, Xfce: exec ck-launch-session startxfce4 (Note that this is only meant for XDM ...) Then there is bug 360987 for internal CK support for XDM And for more information see first post of this thread: http://forums.gentoo.org/viewtopic-t-858965-highlight-consolekit+policykit.html EOF discussion in this bug, move it to the forums post. Thanks.
