Does either Gnome or KDE support Wayland on FreeBSD? [EOM]

[Greg V]

On Mon, Jul 2, 2018 at 1:44 AM, Grzegorz Junka <list1 at gjunka.com> wrote:
> 
> On 01/07/2018 21:48, Greg V wrote:
>> 
>> On Sun, Jul 1, 2018 at 2:45 PM, Grzegorz Junka <list1 at gjunka.com> 
>> wrote:
>>> 
>>> On 30/06/2018 20:37, Johannes Lundberg wrote:
>>>> I don’t know about Gnome or KDE but GTK3 apps work with Wayland. 
>>>> It needs ports built with custom options though.
>>>> 
>>> 
>>> Building ports isn't a problem, however I don't understand how 
>>> particular apps can work with Wayland. I thought that they would 
>>> need to run inside Weston or some other compositor, which in turn 
>>> runs on Wayland? Is the X server in that configuration running as 
>>> a Wayland client with with the GTK3 apps running outside of the X 
>>> server (i.e. are managed by the compositor directly)?
>> 
>> Yes, you can run them inside e.g. Weston or Sway.
>> 
>> Compositors don't run "on" Wayland, Wayland is a protocol.
>> The compositor is the display server, it implements the server side 
>> of Wayland.
>> (Compositors can run in windowed mode under X or under another 
>> Wayland compositor, for development/debugging purposes.)
>> 
>> For backwards compatibility, the X server is indeed running as a 
>> Wayland client, this is called Xwayland, this is optional.
>> 
>> About KDE: I think KDE's kwin_wayland is available now too, but I'm 
>> not sure if it would run directly as the main display server (not 
>> windowed mode) right now on FreeBSD without additional patches 
>> (because of vt/session management stuff -- though maybe ConsoleKit2 
>> might work?).
>> 
> 
> Thanks Greg for the clarification. Let me rephrase it to see if I got 
> it right. Currently FreeBSD supports Wayland compositor in windowed 
> mode under X and this is how the GTK3 applications are running. It 
> might support Wayland as the main display server (not windowed), i.e. 
> using KDE's kwin_wayland, but the status is currently not known.

I'm currently running Weston as the main display server, so that is 
known :)
Well, my fork of weston actually: https://github.com/myfreeweb/weston
Sway 0.x also worked, 1.x (master) should work too, unless they broke 
something.

The only unknown is KDE KWin ("might just work with ConsoleKit2?").
I guess I should look into that, but I'm busy with other stuff..

GNOME is definitely not supported ("needs patching to support 
ConsoleKit2 or some other alternative to systemd-logind").
That's actually the main porting issue in general, many compositors use 
logind, some (like gnome) *only* use logind.

> If that's correct, then assuming that I compiled my ports with 
> support for Wayland enabled, and assuming further that I have 11.2 
> installed, what else would I need to do to be able to test this?
> 
> I guess I need to compile and install drm-next-kmod or 
> drm-stable-kmod. Will either work on generic 11.2 or I need a custom 
> kernel? I guess again that the later should work with the generic 
> kernel but it will only supports Polaris Radeon cards. If I recall 
> correctly Hans Petter Selasky was working on merging support for 
> Radeon Vega (Linux kernel 4.15) into 11-STABLE (future 11.3). If that 
> is correct and the merge was completed then I could compile a custom 
> 11-STABLE kernel and together with the 11.2 userland be able to test 
> windowed Wayland on Vega?

For windowed mode, you don't need anything special.

But for *anything on Vega*, you do need drm-next-kmod.

LinuxKPI updates required for drm-next-kmod 4.15 have indeed been 
merged into 11-STABLE: 
https://svnweb.freebsd.org/base?view=revision&revision=335436

Vega support is still not as stable as <=Polaris, btw:

https://github.com/FreeBSDDesktop/kms-drm/issues/76
https://github.com/FreeBSDDesktop/kms-drm/issues/71

> Please correct if my guesses are wrong. Sorry for all those questions 
> but without the updated wiki it gets a bit confusing :)
> GrzegorzJ