KDE Frameworks 6 & Qt6'ed Gear Apps Will Release Alongside Plasma 6.0 In February

[bug77]

The vast majority of users do not need these things. The vast majority. And at least half of those complaining about those things, do not even use them, they just complain because they want "stuff" and "options" to feel a warm fuzzy feeling in their bellies about using "feature rich software and not be left behind", in theory. Honestly most users can use Wayland right now with no issues at all.

This is about KDE, not Gnome.

[TemplarGR]

Without HDR support, color management support and fractional scaling having just landed (though Gnome had something custom patched in), "working" is kind of a big word.

The vast majority of users do not need these things. The vast majority. And at least half of those complaining about those things, do not even use them, they just complain because they want "stuff" and "options" to feel a warm fuzzy feeling in their bellies about using "feature rich software and not be left behind", in theory. Honestly most users can use Wayland right now with no issues at all.

[Rovano]

Chromium	116.0.5845.96 for Linux Mint (64bit)
User agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36
cmd	/usr/lib/chromium/chromium --disable-features=TFLiteLanguageDetectionEnabled,GlobalVaap iLock --ozone-platform-hint=auto --use-gl=angle --use-angle=gl --enable-features=VaapiVideoDecoder,VaapiVideoEncoder,Vaapi VideoDecodeLinuxGL,UseChromeOSDirectVideoDecoder --video-capture-use-gpu-memory-buffer --enable-native-gpu-memory-buffers --enable-gpu-rasterization --disable-pings --no-pings --flag-switches-begin --flag-switches-end --ozone-platform=x11 --desktop-startup-id=wrapper-2.0/chromium/1768-0-Panter_TIME448370 --origin-trial-disabled-features=WebGPU
way	/usr/lib/chromium/chromium

Graphics Feature Status

• Canvas: Hardware accelerated
• Canvas out-of-process rasterization: Disabled
• Direct Rendering Display Compositor: Disabled
• Compositing: Hardware accelerated
• Multiple Raster Threads: Enabled
• OpenGL: Enabled
• Rasterization: Hardware accelerated on all pages
• Raw Draw: Disabled
• Skia Graphite: Disabled
• Video Decode: Hardware accelerated
• Video Encode: Hardware accelerated
• Vulkan: Disabled
• WebGL: Hardware accelerated
• WebGL2: Hardware accelerated
• WebGPU: Disabled

on X11.


What can it do on Wayland?

[Vistaus]

It seems that all parts of your post is outdated, Falkon is using Chromium 87.0.4280.144 under qt-webengine 5.15.14, there is no true Vulkan support and acceleration in Chromium 87 but there is OpenGL, and all smoothness you experience is actually opengl backend.

Wrong. Vulkan is active, according to chrome://gpu in Falkon (Qt 5). (And there is a Qt 6 port with a newer Chromium version, btw.)

And what's also wrong is the Qt version you reported as Falkon uses QtWebEngine 5.15.15, not 5.15.14. So either you made a mistake or you use an outdated version. But either way, even if you don't like that it's 87.0 based, you can force your own user agent based on a newer version in the settings (I didn't do that, though).

Another known issue is when you use Vulkan backend WebGL is fully broken, even on Xorg, you see? Vulkan isn't yet fully stable on Xorg too, Wayland is currently far away.

Didn't know about that, but I don't use WebGL.

About electron apps, most of them use xwayland by default and it you want native wayland you need to pass switch, which leads to OpenGL ES not Vulkan.

Yes, you need to pass a switch. That's why I posted the instructions.

What i'm talking about is stemming from lots of tests under various systems, so please do not criticize without up-to-date and actual results.

I only criticize when people get things wrong, in your case the part about Falkon and somewhat Electron. Falkon is my daily driver, btw.

[chromer]

What do you mean Chromium has no Vulkan in Wayland? I'm using Falkon with hardware acceleration + Vulkan on Wayland

It seems that all parts of your post is outdated, Falkon is using Chromium 87.0.4280.144 under qt-webengine 5.15.14, there is no true Vulkan support and acceleration in Chromium 87 but there is OpenGL, and all smoothness you experience is actually opengl backend.

Chromium is usable and almost stable on wayland but only with OpenGL ES backend.

Another known issue is when you use Vulkan backend WebGL is fully broken, even on Xorg, you see? Vulkan isn't yet fully stable on Xorg too, Wayland is currently far away.

About electron apps, most of them use xwayland by default and it you want native wayland you need to pass switch, which leads to OpenGL ES not Vulkan.

What i'm talking about is stemming from lots of tests under various systems, so please do not criticize without up-to-date and actual results.

[Rovano]

Without HDR support, color management support and fractional scaling having just landed (though Gnome had something custom patched in), "working" is kind of a big word.

That's right. HDR and color management is beyond me. I forgot about that. So at least something is already in version 4.12.

[devling]

Not sure what you guys are talking about, I use KDE wayland and have for the last 6 months.. Chrome, slack ( / electron softare) etc works 100%, or at least so close to 100 that I haven't noticed any issues. Much less problems now than I had on X.

[Vistaus]

When we talk about readiness of something like wayland, it's not just wayland itself, it's everything we use daily , from complex softwares like Chrome/Chromium to every other feature that is based on protocol.

Chrome/Chromium has lots of lack in wayland : No Vulkan, No Video Acceleration, many issues to address

What do you mean Chromium has no Vulkan in Wayland? I'm using Falkon with hardware acceleration + Vulkan on Wayland and it works great, the entire UI and navigating web pages has never so smooth. And Falkon is based on QtWebEngine, which is Chromium with some added Qt bindings. So Vulkan is, in fact, supported in Chromium on Wayland. But yeah, video acceleration isn't yet.

Also, Electron can use Wayland nowadays, so that part of your post is outdated as well. https://wiki.archlinux.org/title/wayland#Electron

[bug77]

GNOME has been working with Wayland for years. I wouldn't worry about KDE.

Without HDR support, color management support and fractional scaling having just landed (though Gnome had something custom patched in), "working" is kind of a big word.

[Rovano]

Strictly speaking, Wayland is just a protocol, a specification. It has about zero value without proper implementations. Because it chose to be so radical, it can't get away with one implementation, like X, it needs everyone to rewrite their compositors pretty much from scratch. It's over 10 years in the making and it's still debatable whether switching is a net gain. I will probably give it another try when KDE6 releases, but I'm not holding my breath. If it works, I'll consider that a nice surprise. If it doesn't, more of the same.

GNOME has been working with Wayland for years. I wouldn't worry about KDE.