Yes, that matches my research as well.

There is an experimental branch btw https://github.com/sddm/sddm/pull/616

I guess https://source.puri.sm/Librem5/wlroots/blob/librem5-0.6.x/types/wlr_export_dmabuf_v1.c can be used as inspiration for our own implementation.
Added in https://source.puri.sm/Librem5/wlroots/commit/36bd4795d4fe2282dfcc59f26863bac2896a4a3f

What the goal is is not really agreed upon.

This got implemented in https://phabricator.kde.org/D22571, which is flawed (see the various comments there).

In addition to the above, notice that KWin must put server-side decoration around the window geometry, not the main surface.

Alright, let's go quickly over the proposed solution...

Npte that we need both libinput and the wayland protocol to offer Qt/Krita all the information it needs.
https://github.com/wayland-project/wayland-protocols/blob/master/unstable/tablet/tablet-unstable-v2.xml

So, one needed thing ultimately is to extend libinput to reach feature parity with xf86-input-wacom. I know this is not directly part of plasma dev, but this had to be said, and I hope we can get good communication with libinput devs to move forward on that topic.

This task is a duplicate of T6106.

I wouldn't be so sure that co-locating with Plasma makes unequivocally sense. Both @davidedmundson @romangg as well as other people like me have several responsibilities within the project that will definitely be a distraction to the goal. Co-locating with Krita, if they need need ad-hoc work would make sense. Doing it around an upstream conference (QtCS, XDC) would also make a lot of sense.

My two sense about it :

It should be about basic Activities support and virtual desktops matching feature in X.

I've been slowly plugging away at a KCM to manage libinput tablets over here. Making it work on X first before trying to get KWin tablet support up to get it working there too.

Do we need KKeyServer at all on Wayland?

See also D7524.

SuSE still use this "feature" for making plasma run in wayland, and all clients in XCB.

Have not noticed this problem for ages. Above bugs seem to be closed fixed or not reproducible with latest Qt build.

Don't understand what the goal of this task is or how it is supposed to work. Closing as invalid because of that. If somebody can explain pls leave a comment and reopen.

In T4441#200593, @romangg wrote:

@zzag is this task still pending? Can you add some more detail to the description what it is about?

What test clients there are?

What test clients there are?

@zzag is this task still pending? Can you add some more detail to the description what it is about?

Is this still relevant? Is the Font installation KCM the same as the Fonts KCM? Fonts KCM doesn't crash for me.

Not completely sure about the task description but if I understand it correctly they already do that.

This is an outdated task. The plan is at the moment to remove Screens global.

In T11619#200299, @feverfew wrote:

@davidedmundson would be happy to work on this. Do you have the URL to the proposal on the mailing list?

See https://lists.freedesktop.org/archives/wayland-devel/2018-July/038832.html
This link should have been in here long ago for reference.

Where's the best place to get in contact to get this moving (when I have time to)?

@davidedmundson would be happy to work on this. Do you have the URL to the proposal on the mailing list?