Wayland by default in neon dev/unstable after Plasma 5.8
Closed, ResolvedPublic

Description

The Plasma team considers to have neon dev unstable (that is git master) switched to Wayland by default. All other neon editions should stay on X11. This would bring us higher exposure and hopefully more bug reports so that we can stabilize Wayland session.

There are some showstopper issues which will require newer software also in Neon:

  • XWayland 1.19
  • Wayland 1.11 for better stability
  • QtWayland 5.7.1 (currently unreleased)
  • xkbcommon 0.7
  • libinput 1.5
  • SDDM patch to detect if Wayland crashes and revert back to X from d_ed

Also our own software stack still has showstoppers which we need to fix before switching to Wayland by default.

Stable is created from Unstable and this would break that merge process unless we want Neon with Plasma 5.9 to have Wayland by default. Probably needs another ISO for Unstable Wayland

sitter added a subscriber: sitter.Sep 5 2016, 1:40 PM

So I talked with @graesslin and it is conceivably only a matter of changing the desktop file used for the default session, which would make this a manageable diversion we could potentially even do in neon-settings where we have some reverted persistent divergence already.

Maybe we could already start preparing things in Dev/Unstable ? I guess we can build Wayland 1.11 already and perhaps take git snapshots for XWayland 1.19 and hopefully the Qt 5.7.1 stack will be released soon.

We already produce the Plasma Wayland ISO so if there's improvements to that such as new versions they should be done pronto. Getting neon dev/unstable to use it is just a case of adding plasma-wayland and changing the default session

This comment was removed by rwooninck.

Ok. But the above indications means QT 5.7.1, A new Xserver stack. Wayland would be just a minor change.

I guess we could look into building Qt 5.7.1 snapshots already in Unstable to prepare for the official release.

sitter moved this task from Backlog to Discussing on the Neon board.Nov 16 2016, 1:17 PM

Seems to me enablement is not going to land until Feb 2017 https://wiki.ubuntu.com/Kernel/LTSEnablementStack

The kernel team seems to have HWE packages in their PPA though https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa?field.series_filter=xenial

I can't seem to find anything for the X11 stack, so that's a bit of a bummer, so we need to fully build our own stack there (Assuming xwayland actually needs a completely new stack). Exploratory task to attempt building xwayland I guess.

also somewhat immediately necessary are xwayland, xkbcommon and libinput.
https://bugs.kde.org/show_bug.cgi?id=372534
https://bugs.kde.org/show_bug.cgi?id=372533
https://bugs.kde.org/show_bug.cgi?id=372532

sitter updated the task description. (Show Details)Nov 16 2016, 1:44 PM
In T3528#66473, @sitter wrote:

I can't seem to find anything for the X11 stack, so that's a bit of a bummer, so we need to fully build our own stack there (Assuming xwayland actually needs a completely new stack). Exploratory task to attempt building xwayland I guess.

xwayland comes out of the xorg-server source, so I am guessing we'll need a full stack build.

sitter updated the task description. (Show Details)Feb 10 2017, 11:49 AM
sitter moved this task from Discussing to Ready To Do on the Neon board.
sitter triaged this task as Normal priority.
jriddell updated the task description. (Show Details)Feb 10 2017, 12:01 PM
jriddell added a subscriber: davidedmundson.
amunshi added a subscriber: amunshi.May 6 2017, 3:30 AM

Where can I test the wayland support/status? jriddell mentioned that we already have an ISO for it, where can I find it?

newer xwayland and xorg is in this PPA for
https://launchpad.net/~ubuntu-multiseat/+archive/ubuntu/xephyr/+packages
but meh the xwayland-hwe-16.04 package is empty

new wayland is in dev unstable

jriddell updated the task description. (Show Details)May 6 2017, 3:10 PM

xwayland 1.19 is in

jriddell updated the task description. (Show Details)May 8 2017, 10:57 AM

added it to the dev/unstable seed so it'll be on the next iso and we can kill the plasma-wayland ISOs

romangg added a subscriber: romangg.

Default might still take some time. But making all Plasma Wayland packages a dependency on Neon such that a user can directly try it from SDDM seems reasonable for Plasma 5.13. Ok?

This is the case already, on all editions of Neon now you can select Wayland at the SDDM login

sitter closed this task as Resolved.Jul 16 2019, 9:18 AM
sitter claimed this task.

Closing this task for now. We've missed the mark by a bit, and from the neon side things should be more or less in place right now. So, this is mostly blocked on actually having the plasma wayland UX ready for primetime. Or perhaps more importantly, should the requirements change we need to reshuffle the stack anyway, so having a perpetually stuck task serves no purpose.