Wayland Option Now in Neon Dev Unstable ISO by Default

Back in the day I started making a Plasma Wayland ISO to help people try out Plasma on Wayland.  Then we started Neon and the obvious way to create the ISOs became through the Neon infrastructure.  With Wayland becoming closer to be ready to use every day I’ve decided it’s time to scrap the dedicated Wayland ISOs and just install the Wayland session by default on the Dev Unstable ISOs. It’s not yet the default so to give it a try you need to log out, select Wayland session and log in again.  Or install the ISO and select it at login (you’ll need to switch back to X to install, Calamares doesn’t run in Wayland because it wants to run as root which is verboten).

Wayland is pretty much ready to use but the reason we can’t switch to it by default is mostly that some obscure graphics cards may not work with it and it’s hard to implement a detection and fallback for this.  The fonts may be a different size due to differences in the screen dots-per-inch detection and middle mouse button selection paste doesn’t yet work.

Grab the KDE neon Dev Unstable ISO now to try it out.

Jonathan

10 Comment

  1. […] More details via this blog post. […]

  2. […] Wayland Option Now in Neon Dev Unstable ISO by Default […]

  3. We’ll be looking at the Calamares installer under Wayland this coming week. Wayland’s total ”njet” on (setuid) root apps is a real pain in the butt for things that need to run as root — like text editors for editing system files, sometimes, or installers. For me the least-desirable — but possibly best in terms of long-term Wayland compatibility — would be to move all the root-needing things to external non-gui applications, but that’s likely to produce a fistful of setuid executables for doing everything from scanning for attached disks (and their partition tables) to setting the time zone.

    There’s a workaround in Wayland on Neon, though , and that’s because sudoedit is a terrible kludge. Pretend konsole is an editor, and then run Calamares from that root konsole.

    1. The thing is, it’s more complicated than that, some GUI apps actually do something when run through kdesu and/or pkexec in Wayland sessions, some have strange issues (that do not look like just a failure to connect to the compositor at all), it might also depend on the distro and the compositor.

  4. […] с актуальными версиями программ и компонентов KDE, объявили об интеграции поддержки сеанса на базе Wayland в основные […]

  5. […] с актуальными версиями программ и компонентов KDE, объявили об интеграции поддержки сеанса на базе Wayland в основные […]

  6. Charles Tersteeg says: Reply

    It’s unlikely middle paste will ever work as the clipboard of x and Wayland are different.

    1. GNOME actually defined a protocol extension that allows middle-click paste, but at least KWin does not implement it yet.
      https://bugs.kde.org/show_bug.cgi?id=373907

      The problem is that GNOME implemented it the usual GNOME way, by defining their own standard without actually standardizing it, and that the KWin maintainer refuses to implement anything non-standard. So now this useful feature is blocked on politics.

  7. OlafLostViking says: Reply

    Hi, is “QXL/Spice” one of these obscure graphics cards or can we expect this to work one day (optimally including resizing the VM window) with Plasma/Wayland? Thanks!

    1. Jonathan Riddell says: Reply

      no idea sorry

Leave a Reply