I've been running Neon Wayland on my laptop. My experience so far is as follow:

1. It is not yet robust in the sense if you change much of anything it tends to crash. For example switching from task manager to icons only task manager caused a crash. Also wayland doesn't seem to like you installing new desktop themes either.

2. The fonts seem unusually large at times even with a font setting of 96 dpi.

3. The desktop is quite slow to load from the splash screen. When you think it has loaded and it really hasn't, if you click the touchpad it will crash.

4. I like tap to click on my touchpad, but trying to configure that in systemsettings5 causes systemsettings5 to crash and usually the plasma shell
as well. I have been unable to get tap to click.

5. Initially, I often caused crashes and after rebooting all I got from plasma wayland was a black sreen and blinking cursor. I found that reinstalling plasma-wayland-desktop would allow me get back into wayland after rebooting.

Having said all that, I would say that wayland is quite responsive and browsing the web works well (using firefox). I am looking forward to further development.

willt wrote:I've been running Neon Wayland on my laptop. My experience so far is as follow:

1. It is not yet robust in the sense if you change much of anything it tends to crash. For example switching from task manager to icons only task manager caused a crash. Also wayland doesn't seem to like you installing new desktop themes either.

Instability is still a known issue. We are trying hard to iron them out. So whenever a crash happens, please report the crash! If we have the backtrace it's easy to fix.

willt wrote:2. The fonts seem unusually large at times even with a font setting of 96 dpi.

The font setting is ignored. Set the env variable: QT_WAYLAND_FORCE_DPI. See also https://phabricator.kde.org/D1605 which I created today

willt wrote:3. The desktop is quite slow to load from the splash screen. When you think it has loaded and it really hasn't, if you click the touchpad it will crash.

Please report the crash.

willt wrote:4. I like tap to click on my touchpad, but trying to configure that in systemsettings5 causes systemsettings5 to crash and usually the plasma shell
as well. I have been unable to get tap to click.

Touch pad configuration is still missing, see also my latest blog post https://blog.martin-graesslin.com/blog/ ... inwayland/

willt wrote:Having said all that, I would say that wayland is quite responsive and browsing the web works well (using firefox). I am looking forward to further development.

Thanks for the feedback. But pretty please report the crashes. That would help a lot as then we can fix them.

Thanks for your feedback!

willt wrote:1. It is not yet robust in the sense if you change much of anything it tends to crash. For example switching from task manager to icons only task manager caused a crash.

Task Manager is heavily WIP right now but just yesterday one major crash we had in there was fixed.

willt wrote:2. The fonts seem unusually large at times even with a font setting of 96 dpi.

Yes, something with font scaling / dpi scaling is still off at the moment.

willt wrote:3. The desktop is quite slow to load from the splash screen.

The splash screen waits for KWin (the window manager) to start but on a Wayland session it's the first thing that starts, so it just times out eventually.

willt wrote:4. I like tap to click on my touchpad, but trying to configure that in systemsettings5 causes systemsettings5 to crash and usually the plasma shell
as well.

Implementing configuration for input devices has just recently begun, see Martin's Blog post for more information. In essence some basic configuration like mouse acceleration works now but touchpad config is pretty much non-existent as of now.

It is still quite some work to be done but one can already see light at the end of the tunnel

kbroulik wrote:

willt wrote:3. The desktop is quite slow to load from the splash screen.

The splash screen waits for KWin (the window manager) to start but on a Wayland session it's the first thing that starts, so it just times out eventually.

I just fixed that.

I sometimes try switching to Plasma wayland. But i am always forced to switch back to X11 since performance degrades too much. If performance was a bit better i could actually use the wyaland desktop.

In 2018, with newest Neon (5.12.4 at present), I myself find that I can use Wayland with KDE neon GNU/Linux most of the time for all sorts of things. And I find that it is fast and elegant in mostly all operations. Except when there is a particular program--such as Linphone from Linphone.org--that either hasn't been updated to handle Wayland correctly or I haven't found out how to get the right version yet. In such cases only I switch to an xorg login.

One workaround that could belong to this thread is this: when such as Firefox ceases to respond--which happens quite often when I open many tabs in Firefox and do a lot of things on the net--then all is well if one only gets to close the program. It doesn't seem to work to click on the X of the window frame of a stalled program. However, one can force any such program to close (unless one uses a process manager like KSysGuard) by a simple command, if one has the exact name of the program:

Code: Select all

pkill -x firefox


After this, when Firefox is restarted, it will usually work splendidly and possibly one can carry on from where one left. This means that Neon doesn't have to be rebooted all that often when one uses Wayland intensely. I should hope, however, that somehow, in a future Neon version, it will come a way in which a click on the X on the window is enough to open a question about 'force quit', as this doesn't seem to normally happen in the present version of Neon. Apart from some such minor issues, I think Neon with Wayland is the best Linux around.

mgraesslin wrote:

willt wrote:I've been running Neon Wayland on my laptop. My experience so far is as follow:

willt wrote:4. I like tap to click on my touchpad, but trying to configure that in systemsettings5 causes systemsettings5 to crash and usually the plasma shell
as well. I have been unable to get tap to click.

Touch pad configuration is still missing, see also my latest blog post https://blog.martin-graesslin.com/blog/ ... inwayland/

Today, on Plasma 5.15, is the touch pad configuration still missing?