KDE Will Prioritize Wayland, Consistency & Apps Over The Next Two Years

[loganj]

does wayland prevent usage of vulkan? or this happens only on nvidia cards?
after enabling wayland on kde or gnome dxvk/d9vk stop working. lutris also says that no vulkan is installed

[AsuMagic]

I tried KDE on Wayland pretty recently (latest Arch packages, RX 580). It wasn't a great experience:

• Some glitchiness related to pop-ups appearing in the wrong place (okay, whatever).
• Screen configuration messed up, only my secondary screen appears and I cannot get my primary monitor to run at 75Hz. It... quite already makes it worthless for me.
• Hangs when starting some apps...

I am in the process of switching to sway now. Things are in a much better state there. I wouldn't call it perfect but it is pretty darn impressive:

• VRR is not supported. It seems to be a WIP however, and FWIW I can't even get it to work on X11 because I have two monitors. Hopefully multiple monitor support should be better on sway (and Wayland in general) than on X11. When it works, then I have a very very good reason to use Wayland over Xorg.
• Windows flicker when doing certain actions, e.g. sometimes when opening windows.

... And shockingly enough, that's quite about it. Firefox feels smoother to use (native Wayland, tweaked smooth scroll, WebRender forced on).

[archkde]

Interesting. I'm using a KDE Wayland session as my daily driver and there's only 3 bugs I have with it:
1. I can't seem to take a rectangular screenshot with Spectacle no matter how hard I try
2. Yakuake can't show up on my second monitor for some reason
3. Firefox running natively on Wayland visually glitches any other windows that appear on top of it

1 and 2 are minor annoyances at best, with 3 most likely being a problem with Firefox instead of KWin. I wonder what issues other users are having.

3 is probably the subsurface clipping bug in KWin. It happens with other applications, too.

[Jedibeeftrix]

vulkan renderer

[shmerl]

Good!

I'd like to see these in the Wayland support in KDE / KWin:

1. Fixing the long standing subsurfaces clipping bug.
2. Adaptive sync support.
3. Support for Wacom drawing tablets (which work well with Xorg).
4. Vulkan renderer.

[Daktyl198]

Interesting. I'm using a KDE Wayland session as my daily driver and there's only 3 bugs I have with it:
1. I can't seem to take a rectangular screenshot with Spectacle no matter how hard I try
2. Yakuake can't show up on my second monitor for some reason
3. Firefox running natively on Wayland visually glitches any other windows that appear on top of it

1 and 2 are minor annoyances at best, with 3 most likely being a problem with Firefox instead of KWin. I wonder what issues other users are having.

[phoenk]

Wayland default is remaining on the Fedora roadmap. So November another roll of dice.

https://fedoraproject.org/wiki/Releases/31/ChangeSet#Qt_Wayland_By_Default_On_Gnome

Yes you need to catch up 144hz Fedora is in the process of turning off gtk and qt applications from being able to use X11.

So Fedora move to Wayland is well and truly underway. Having broken wayland support is going to hurt.

Wayland has been default in Fedora for a few years now. That change is specifically to have QT applications be wayland-native by default, rather than through XWayland. GTK apps have been wayland-native since Fedora 25.

[TheLexMachine]

When I used KDE several years ago, before switching to Ubuntu MATE, many of the KDE apps intended specifically for use with KDE were the open-source equivalent of abandonware and hadn't seen any real code updates in years. Has that changed?

[oiaohm]

Problem is they already down priortized x11. No Fedora to move wayland ahead. No Ubuntu to keep x11 rocking.

Wayland default is remaining on the Fedora roadmap. So November another roll of dice.

https://fedoraproject.org/wiki/Releases/31/ChangeSet#Qt_Wayland_By_Default_On_Gnome

Yes you need to catch up 144hz Fedora is in the process of turning off gtk and qt applications from being able to use X11.

So Fedora move to Wayland is well and truly underway. Having broken wayland support is going to hurt.

[gbcox]

A focus on consistency and KDE apps sounds great too. I hope they will split KDE Applications in core and experimental packages. Kicker should go to trash, unstable applications should be moved out of the core packages making it clear that they must be improved (e.g. Kmail), get rid of Konqueror in favor of Falkon (why do we need 2 browsers?), make sure that the user will see much less KDE Plasma or application crashes, provide one nice music player that actually works, make breeze visually nice and clean, enforce a consistent app look and feel, remove the need for a new user to first customize KDE before it looks and works fine, promote beautiful applications like latte-dock, provide an easy backup utility, provide a profile sync for multiple machines e.g. based on Nextcloud, get rid of stupid messages like when opening a Nextcloud webdav folder, improve the bug reporting utility, make multi monitor setups work, do not copy files twice when copying them to a network location, improve touchscreen usage, make notifications less annoying, allow fractional scaling on Wayland, let flatpak applications work fine on Wayland, ... and last but not least improve stability.

I was under the impression that the official browser for KDE was now Falkon, which is quite good. IMO the main thing that is holding back Falkon adoption is that qt webengine still doesn't support chrome extensions - and most people want their extensions. On the application front they should have long ago replaced JuK with QMMP - just from the fact that JuK goes years without any updates and QMMP is a extremely active project. They should also adopt CopyQ as their clipboard manager for the same reason.