|Commit message (Collapse)||Author||Files||Lines|
The Plasma Wayland session script already does this. Without it, you
will notice that DBUS_SESSION_BUS_ADDRESS is not getting set and for instance
Chromium can no longer connect to KWallet via D-Bus.
Using elogind will enable a fully working Wayland session for KDE Plasma5.
kwayland, plasma-framework in frameworks
kdeconnect-framework in plasma-extra
And I refreshed all of the Plasma packages.
The variable SLACKPAM is set to "yes" in kde/kde.options if PAM is found
installed on the system. Otherwise it is set to "no" and this is meant
to add support for PAM.
These packages will be supplied by a pam-ified Slackware, so they should not
be installed from 'ktown':
These packages will react to SLACKPAM variable setting:
Uncomment in kde/modules/plasma and compile:
The newest Plasma desktop is no longer started with /usr/bin/startkde
but with /usr/bin/startplasma-x11 and so the custom X startup scripts
that are installed with the plasma-workspace package needed to be updated.
In an attempt to keep a single source tree for both 'latest' and 'testing'
repositories, everything to support a Plasma5 Wayland session was added.
This was made possible *without* the need for PAM or systemd because the
ConsoleKit2 and KWin developers cooperated (on my request :-) to add the
logind DBus API to CK2 and make KWin accept CK2 as an alternative to
systemd-logind if the latter is not present.
Note that this requires recompilation of two stock Slackware
packages, mesa and xorg-server, to let them gain Wayland support.
- wayland and wayland-protocols
In order to start a Wayland session (you'll need to use packages from the
'testing' repository) either run 'startkwayland' from your console prompt in
runlevel 3, or choose the "Plasma (Wayland)" session in the SDDM dropdown
if you are booting into runlevel 4.
Use an additional "dbus-launch --sh-syntax --exit-with-session" to exec
the startkde script.
The KDE 5 Software Compilation no longer exists as such.
The components are now:
- Frameworks 5.2.0
- Plasma 5.0.2
These packages need to be installed on top of the most recent KDE 4.14.x
because Applications tarballs which build on top of Frameworks and
Plasma have not yet been released.