GNOME 3.29.2 Released As The Second Step Towards GNOME 3.30

[phoronix]

Phoronix: GNOME 3.29.2 Released As The Second Step Towards GNOME 3.30

GNOME 3.29.2 is now available as the second development release on the road towards this September's release of GNOME 3.30...

http://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.29.2-Released

[aufkrawall]

Still no automatically adjusted fps/refreshrate with Mutter on Wayland?
Is a Wayland session still considered to be a technical preview, or what would be the explanation?

[PluMGMK]

Wayland session still breaks quite often on my end. (In fact it's currently unusable for some reason, seemingly since I updated Mesa at one point…)

[uid313]

Is the window slide animation fixed when using the window positioning shortcut keys? Ctrl+Alt+4, Ctrl+Alt+6, etc?

Does GNOME on Wayland still rely on XWayland, or is it now possible to run it without any dependency on X?

I wish the gnome-shell-extension-tool would generate JavaScript ES6 classes.

[Brisse]

Wayland session still breaks quite often on my end. (In fact it's currently unusable for some reason, seemingly since I updated Mesa at one point…)

Yea, it broke for me recently on Debian Sid when I received GNOME 3.28.1 but then I added amdgpu.dc=1 to my kernel boot parameters and it started working again. It's completely broken without that boot parameter though.

[TemplarGR]

Still no automatically adjusted fps/refreshrate with Mutter on Wayland?
Is a Wayland session still considered to be a technical preview, or what would be the explanation?

Doesn't matter what it is considered to be. Wayland is going to be a freaking mess for the next decade at least, while providing no tangible benefit to end users. It is a disaster. They might as well just put the effort into redesigning X. The major issues Wayland was supposed to solve were solved by DRI3, Wayland has no reason to exist now other than the NIH syndrome. Any additional issues with X could be solved procedurally over the years instead of just abandoning for a retarded solution that still isn't production ready after a decade and will probably never be.

[cybertraveler]

Doesn't matter what it is considered to be. Wayland is going to be a freaking mess for the next decade at least, while providing no tangible benefit to end users. It is a disaster. They might as well just put the effort into redesigning X. The major issues Wayland was supposed to solve were solved by DRI3, Wayland has no reason to exist now other than the NIH syndrome. Any additional issues with X could be solved procedurally over the years instead of just abandoning for a retarded solution that still isn't production ready after a decade and will probably never be.

Wayland has been hugely successful. There are huge numbers of programs, libraries, toolkits that have adopted it. There are multiple Wayland server implementations and the work on making Wayland viable has never once ceased: the pace of improvement to Wayland is only increasing.

There are huge advantages to using Wayland. Some of them being:

- It does not have to be backwards compatible with decades worth of X apps. This means they can create a clean, simple design (not a mess as you described it). This makes implementing Wayland easier. This means you are less likely to get bugs and less likely to get security issues than if you were to simply forever build ontop of X.

- Wayland provider far better support for isolation of clients. This has practical security benefits including: your browser app can't read the keystrokes going to your text editor app or your password manager app. This has not been practically implemented on X in a way that most X users can benefit from. It might be because practically implementing it on X could require a large redesign of X. What is Wayland, if not: a large redesign of X. There are Xorg developers working on Wayland to make it everything they wish Xorg could be.

- Wayland is designed to work well with real, modern hardware. It's not focused on supporting outdated hardware designs or hypothetical future designs which may never be built because they are impractical. This again has the benefit of allowing Wayland to be a more simple design that is very much fit for purpose.

- Practically speaking, X is failing in many areas which should not be a problem in 2018. One example is how X badly handles full screen applications, lock screens and screensavers. Wayland has been specifically designed to make these 3 things just-work and without any hacks or corner-case issues. There's actually a phoronix article on this: https://www.phoronix.com/scan.php?pa...item&px=OTI5MQ

Wayland isn't finished yet, but we are far enough along that all the popular GUI toolkits can natively speak it, lots of the popular desktop environments can serve as Wayland compositors and special efforts have been made or are being made on loads of the most popular programs to make them work well on Wayland (eg Firefox).

I for one am looking forward to running a lighter, more graceful, more secure and potentially faster desktop environment in the future that is built with the Wayland protocols. Wayland wont be perfect but it will be better than X and will make a GNU/Linux desktop more competitive with a Mac OS X and Windows desktop.

[aufkrawall]

Practically speaking, X is failing in many areas which should not be a problem in 2018. One example is how X badly handles full screen applications, lock screens and screensavers. Wayland has been specifically designed to make these 3 things just-work and without any hacks or corner-case issues. There's actually a phoronix article on this: https://www.phoronix.com/scan.php?pa...item&px=OTI5MQ

In practice, the mentioned fields by you work fine on Xorg, while they usually don't with the existing Wayland compositors. I don't see any groundbreaking progress with Plasma or Gnome on Wayland over the past year, it's still astronomically far from meeting my expectations.

[Brisse]

In practice, the mentioned fields by you work fine on Xorg, while they usually don't with the existing Wayland compositors. I don't see any groundbreaking progress with Plasma or Gnome on Wayland over the past year, it's still astronomically far from meeting my expectations.

I have to agree with this from a users perspective. I think cybertraveler did well to point out why Wayland is needed, but the current implementations are, despite a decade of development, very immature and every time I receive an update related to desktop compositing and Wayland I more often see things being more and more broken rather than fixed.

[TemplarGR]

Wayland has been hugely successful. There are huge numbers of programs, libraries, toolkits that have adopted it. There are multiple Wayland server implementations and the work on making Wayland viable has never once ceased: the pace of improvement to Wayland is only increasing.

There are huge advantages to using Wayland. Some of them being:

- It does not have to be backwards compatible with decades worth of X apps. This means they can create a clean, simple design (not a mess as you described it). This makes implementing Wayland easier. This means you are less likely to get bugs and less likely to get security issues than if you were to simply forever build ontop of X.

- Wayland provider far better support for isolation of clients. This has practical security benefits including: your browser app can't read the keystrokes going to your text editor app or your password manager app. This has not been practically implemented on X in a way that most X users can benefit from. It might be because practically implementing it on X could require a large redesign of X. What is Wayland, if not: a large redesign of X. There are Xorg developers working on Wayland to make it everything they wish Xorg could be.

- Wayland is designed to work well with real, modern hardware. It's not focused on supporting outdated hardware designs or hypothetical future designs which may never be built because they are impractical. This again has the benefit of allowing Wayland to be a more simple design that is very much fit for purpose.

- Practically speaking, X is failing in many areas which should not be a problem in 2018. One example is how X badly handles full screen applications, lock screens and screensavers. Wayland has been specifically designed to make these 3 things just-work and without any hacks or corner-case issues. There's actually a phoronix article on this: https://www.phoronix.com/scan.php?pa...item&px=OTI5MQ

Wayland isn't finished yet, but we are far enough along that all the popular GUI toolkits can natively speak it, lots of the popular desktop environments can serve as Wayland compositors and special efforts have been made or are being made on loads of the most popular programs to make them work well on Wayland (eg Firefox).

I for one am looking forward to running a lighter, more graceful, more secure and potentially faster desktop environment in the future that is built with the Wayland protocols. Wayland wont be perfect but it will be better than X and will make a GNU/Linux desktop more competitive with a Mac OS X and Windows desktop.

I don't know where you are living currently but it is not planet earth.