Open dilyn-corner opened 4 years ago
The first issue I have encountered: I cannot start a Wayland session.
@sdsddsd1, tips or tricks?
I dont have a kde-system anymore, but I am glad to give my "expertise" :D
What are prerequisites you have already done? Like do you start with elogind, from tty or sddm? Without elogind the xdg_runntime_dir needs to be set. Things you probably know with your wl experience but just to make sure.
Going after KDE docs https://community.kde.org/KWin/Wayland#Start_a_Plasma_session_on_Wayland
dbus-run-session startplasma-wayland
Just a TTY for now :)
I thought I had done all of these things but I will retest.
Presumably forking xorg-server
to add xwayland support will be necessary for now, but we'll see!
I am just snooping around (: What do you try do start, kwin or kwinft? Arch wiki references to the same docs I found above https://wiki.archlinux.org/index.php/KDE#From_the_console . Arch also provides a "kde wayland" package. May be good to look over this. https://www.archlinux.org/packages/extra/x86_64/plasma-wayland-session/
Their package only installs a .desktop file, which might be relevant.
The error I'm actually getting that seems to stop this is "no libinput :(". Which is a weird error to get.
I noticed that kwayland
and plasma-wayland
is missing as a package in the plasma repo.
kwayland
is in frameworks and plasma-wayland
is not a package (though *-session
and *-protocols
are, and we have discussed the former and the latter is in this repo).
As it stands, a pseudo list of currently required xorg libs:
kscreenlocker
-> qt5-x11extras
, xcb-util-keysyms
kwindowsystem
-> qt5-x11extras
libkscreen
-> qt5-x11extras
plasma-integration
-> qt5-x11extras
plasma-desktop
-> xorg-server
kwin
-> libX11
kwayland
-> EGL. This means mesa
requires x11 platform support
There are a few more small deps sprinked in (like xcb-util-*
stuff), but ultimately it all comes down to when kwayland
stops being... Dumb? Like, that's the dumbest framework ever. It's literally named kWAYLAND for crying out loud.
kwin
has a sneaky line in its build output:
xwayland required to launch kwin_wayland
This can't be it, right?
Will test, of course 🙃
Update: have tested all changes thus far. No longer have the aforementioned issue about libinput. Which is good. New issue: session appears to launch, but it is merely a black screen. What fun.
Thats some progress.🍹 Looking for 'kwin blackscreen' brings up mostly issues related to nvidia. And also issues 4 years old :\ 💻 🧑🚒
With the release of
plasma 5.20.0
, Wayland support is at the fore. This issue exists to track progress on dropping Xorg dependencies. Currently it should be perfectly possible to start a Wayland session. Any issues relating to better Wayland support in this repository will be documented here.