handbook: Update instructions for starting ConsoleKit

[jbeich]

documentation/content/en/books/handbook/wayland/_index.adoc

78

Looks incorrect. --exit-with-x11 may not work under Wayland because kwin_wayland (via startplasma-wayland) hasn't started yet thus Xwayland hasn't created X11 socket. Also, ck-launch-session creates XDG_RUNTIME_DIR that DBus may want to read service activation files from or (non-default) place its socket in.

$ env -u DISPLAY XDG_RUNTIME_DIR=$(mktemp -dt xdg-run) dbus-launch --exit-with-x11 ls
Session lifetime based on X11 requested, but X11 initialization failed.

$ su root -c "sed -i '' 's,<busconfig>,&<listen>unix:runtime=yes</listen>,' /usr/local/etc/dbus-1/session.conf"
$ XDG_RUNTIME_DIR=$(mktemp -dt xdg-run) dbus-launch --exit-with-x11 ls
$ find /tmp/xdg-run.*
/tmp/xdg-run.uaOGy3WV/
/tmp/xdg-run.uaOGy3WV/dbus-1
/tmp/xdg-run.uaOGy3WV/dbus-1/services
/tmp/xdg-run.uaOGy3WV/bus # see unix:runtime=yes above

[arrowd]

documentation/content/en/books/handbook/wayland/_index.adoc

78

Looks incorrect. --exit-with-x11 may not work under Wayland because kwin_wayland (via startplasma-wayland) hasn't started yet thus Xwayland hasn't created X11 socket.

I know nothing about wayland, so you're most likely right on this.

Also, ck-launch-session creates XDG_RUNTIME_DIR that DBus may want to read service activation files from or (non-default) place its socket in.

I didn't get that part. What does this entail?

[jbeich]

documentation/content/en/books/handbook/wayland/_index.adoc

78

It changes behavior and breaks bug 279743. ck-launch-session will clobber XDG_RUNTIME_DIR on the first session, effectively removing DBus socket there and (infrequently used) session-specific autostarted services. consolekit2 uses system bus (started by dbus_enable=YES), not session bus (started via dbus-launch or dbus-run-session).