Bug 597774

Summary:	Missing logind API for Plasma wayland?
Product:	Gentoo Linux	Reporter:	Petross404(Petros S) <petross404>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED NEEDINFO
Severity:	enhancement	CC:	kensington
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Petross404(Petros S) 2016-10-22 13:53:45 UTC

startplasmacompositor in VT should fire up a wayland session of Plasma, but it doesn't. After all it seems to be the lack of certain API's to make a wayland session impossible.

https://blog.martin-graesslin.com/blog/2016/07/why-does-kwin_wayland-not-start/


Another workaround is to install elogind. But it currently is located under kde overlay.
https://forums.gentoo.org/viewtopic-t-1039678-start-0.html

Comment 1 Mike Gilbert gentoo-dev

2016-10-23 18:36:52 UTC

This certainly has nothing to do with sys-apps/dbus itself. It only provides the message bus infrastructure. Any APIs are provided by other packages.

Comment 2 Mike Gilbert gentoo-dev

2016-10-23 18:38:53 UTC

Please provide enough information for a developer to actually take some action.

Comment 3 Petross404(Petros S) 2016-10-23 20:34:24 UTC

A plasma wayland session needs logind interface in order to work. This interface can either be provided via systemd, or via a standalone executable - the elogind project which is available in kde overlay.

My point here is that if a user wants to run Plasma with wayland (kwin_wayland etc) should have the option to choose whether he/she wants systemd or not. If not, elogind should be provided by the portage tree as an official solution.

In other words, more testing and support about wayland and Plasma should be taken under consideration. But that's just my opinion of course. :)