A Look At The Exciting Features/Improvements Of GNOME 3.22

[dragon321]

Can it run Qt5 based application as wayland clients? Plasma 5.8 supports running GTK3 applications natively on Wayland.

I haven't got any problems with that. Just run Qt5 app with -platform wayland parameter and it should works without problems. But window decorations are different than GTK or XWayland applications.

Plasma 5.8 doesnt even run on wayland at all. It doesnt support EGLStreams.

Doesn't run on nVidia prioprietary driver. It works on open source drivers. EGLStreams isn't mandatory for Wayland, there are another way - GBM which is used by all Wayland compositors (GNOME, KDE, Weston etc.). Nobody support EGLStreams now, and that's why Plasma (and any other Wayland compositor) can't run on nVidia driver - it hasn't GBM implementation, but open source drivers has it.

[dragon321]

Can it run Qt5 based application as wayland clients? Plasma 5.8 supports running GTK3 applications natively on Wayland.

Yes, why not? I haven't got any problems with Qt5 apps in GNOME Wayland. Just run application with -platform wayland parameter. There is one problem: Window decoration is different than GTK3 or XWayland applications.

Plasma 5.8 doesnt even run on wayland at all. It doesnt support EGLStreams.

Doesn't run on nVidia prioprietary driver. It works good on open source drivers. And not only Plasma, but all Wayland desktop environments (GNOME, KDE, Weston etc.) can't run on nVidia driver, because it hasn't got GBM implementation which is used by all Wayland compositors instead of EGLStreams. EGLStreams isn't mandatory for Wayland, you can use GBM too. Nobody support EGLStreams now.

[doom_Oo7]

Plasma 5.8 doesnt even run on wayland at all. It doesnt support EGLStreams.

The latest versions of Qt 5 does support EGLStreams so maybe it'll come...

[danielnez1]

Have they fixed the problems with some of their programs breaking due to web providers changing their APIs?

[SpyroRyder]

Have they fixed the problems with some of their programs breaking due to web providers changing their APIs?

That's not a particularly fixable problem, if the API goes dead then so would your program. The mapping tiles thing also came almost out of nowhere so there wasn't a good way they could plan around that

[Marionette]

The screen flickering is likely to be an Intel driver bug actually.

It's not because it was working fine with 4.6 then I upgraded mutter and the gates of hell opened. Also in the bug report there are users user that experience the issue with raedon and nvidia as well.

[oleid]

strange, works for me @ radeon.

[Marionette]

strange, works for me @ radeon.

what distro are you using ? maybe its a debian related bug

[adi_]

It's not because it was working fine with 4.6 then I upgraded mutter and the gates of hell opened. Also in the bug report there are users user that experience the issue with raedon and nvidia as well.

Just to make sure it's not related to Intel Graphics driver (PSR enabled by default from 4.6 onwards) can you try disabling PSR? You can do that by adding i915.enable_psr=0 as a kernel parameter which can be easily done by editing the GRUB entry you are using to boot your machine.

[Marionette]

Just to make sure it's not related to Intel Graphics driver (PSR enabled by default from 4.6 onwards) can you try disabling PSR? You can do that by adding i915.enable_psr=0 as a kernel parameter which can be easily done by editing the GRUB entry you are using to boot your machine.

Nope, same issue. The "flickering" is like a doubl ebuffering issue - it seems that the buffers are not swapped correctlu because it's constantly switching between two images. FOr instance switching between the GDM screen and my desktop. Then a few moments later between my desktop and firefox, etc.