# KWin\_wayland and old ConsoleKit

**URL:** <https://discuss.kde.org/t/kwin-wayland-and-old-consolekit/49009>\
**Category:** Development\
**Tags:** kwin, wayland\
**Created:** [July 29, 2026, 2:31pm UTC](https://discuss.kde.org/t/kwin-wayland-and-old-consolekit/49009 "2026-07-29T14:31:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rjvbb](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/rjvbb/32/33067_2.png) [@rjvbb](https://discuss.kde.org/u/rjvbb)\
**Post date:** [July 29, 2026, 2:31pm UTC](https://discuss.kde.org/t/kwin-wayland-and-old-consolekit/49009/1 "2026-07-29T14:31:19Z")

</div>

I maintain a retro system with a nice “Frankunbuntu” that has a collection of KF5 applications which I run under a Plasma4 environment, including KWin5 as the WM. I picked up the idea somewhere to try to launch a parallel, Wayland desktop session by starting kwin\_wayland from a console tty.

That doesn’t work because my system uses an old ConsoleKit and Ubuntu’s systemd “shim”, so I don’t have the required `TakeDevice` methods on the system DBus.

My account has R/W access to the `/dev/dri/card0` device so I strongly suspect that it should be possible to open the device in a sufficient way from within KWin\_wayland itself.

The question is, can that be done without affecting the main X11 session, and if so, how?

NB: I’m the only user on this system, so any security implications of this kind of hack are probably moot.