If you have time, can you test Enlightenment with their Wayland compositor and report back?
You may have to build from GIT, but they have instructions/scripts for that. On Fri, May 20, 2016 at 8:47 PM, karu.pruun <[email protected]> wrote: > I've tested KDE in the sense of running a KDE application (kile) using > XWayland. It's like using GNOME or XFCE or MATE to run a KDE > application. > > Running a full fledged KDE with XWayland (startkde4) did not go well; > basically you already have a minimal native DE, i.e. Weston, and then > you run another DE, i.e. KDE on top of XWayaland --- KDE was > unusuable, even kile did not start; whereas running just kile as > above, i.e. just as an application with Weston gave a functional app. > > The KDE effort to rewrite KDE for Wayland is documented here > > https://community.kde.org/KWin/Wayland > > As far as I understand all of the major desktop environments are > currently in transition of adding native support to Wayland. Until > this is done, that is, until they do not run natively under Wayland > one has to use a compatibility backend like XWayland to run > applications that rely on Xorg. > > Cheers > > Peeter > > -- > > > > On Fri, May 20, 2016 at 4:08 PM, PeerCorps Trust Fund > <[email protected]> wrote: >> Hi Peter, >> >> This is quite interesting. Have you tested KDE at all with that >> configuration? >> >> >> On 05/20/2016 04:05 PM, karu.pruun wrote: >>> >>> Hello >>> >>> So I compiled Xorg with XWayland support and got it working: many >>> applications that need Xorg work now with wayland/weston. Basically, >>> Xwayland is the "Xorg" for applications that need Xorg; it's a >>> compatibility option as long as an application does not work with >>> wayland/weston directly. >>> >>> I followed directions on this page: >>> >>> https://wayland.freedesktop.org/xserver.html >>> >>> and recompiled x11-servers/xorg-server with options given on that >>> page. It does not compile cleanly but complains about a missing >>> file/library; so before compiling, don't uninstall your xorg-server >>> yet. When the error occurs, I manually copied the file to the build >>> directory in /usr/obj/. . . (see what is the file and the directory in >>> error message) and then remove the xorg-server package. Then "make >>> install" worked fine. (Someone know how to fix this issue?) I then >>> used the attached weston.ini (save to ~/.config/ and edit paths of >>> files like background etc) and manually created >>> >>>> mkdir /tmp/.X11-unix >>> >>> >>> and then (from webapage >>> https://github.com/DragonFlyBSD/DeltaPorts/pull/123) >>> >>>> sudo kldload i915 >>>> mkdir /tmp/wayland_xdg >>>> chmod 0700 /tmp/wayland_xdg >>>> env XDG_RUNTIME_DIR=/tmp/wayland_xdg weston-launch -- --use-pixman >>> >>> >>> Applications that seem to work and are stable (there might more but >>> haven't tried): >>> >>> gtk3: >>> - gedit >>> - nautilus >>> - evince >>> >>> xfce4: >>> - xfce4-terminal >>> - atril >>> >>> - firefox >>> - spyder >>> - scilab >>> - kile (crashes first but works when launched again) >>> >>> Doesn't work: >>> - chrome (segfault) >>> >>> Weston is quite minimalistic but does provide a stable working >>> environment. No tearing and runs smoothly: >>> >>> weston: >>> - has workspaces (switch: super + F1, F2 etc) >>> - a panel with launchers >>> - switch between apps: super (or ctrl) + tab >>> - but: no tray for minimized apps: they can be brought back by >>> switching between apps >>> - Copy-paste works in X and between X and weston >>> - X cursor could be better configured? >>> >>> In summary: I am very much impressed. On this machine, wayland/weston >>> feels faster than X. It's stable, or at least so far. With Xorg I >>> can't switch between VT and graphical screen more than twice; the >>> screen hangs after two switches. With Wayland it just works. >>> >>> I wonder if one might get a minimal DE like Maynard running. It seems >>> to need wayland support in gtk30. >>> >>> Cheers >>> >>> Peeter >>> >>> -- >>> >>
