GNOME Shell + Mutter 40 Beta Released With Wayland Improvements, Overview Redesign

[pal666]

Pointing out actual and factual issues, blocking or not, inconsistencies and design shortcomings is whining?

pointing out your misconceptions framed as those is whining

[qarium]

moron, the only wayland mentioned in article is xwayland, which is x11 server. and improvement was "don't run it unconditionally, run it only when user runs x11 app". which means now enough users aren't using x11 apps at all. sorry that wayland crapped into your pants again

absolutly right... this full moron is just anti-wayland because his loved nvidia card does handle it like shit.

people like this moron is just poison for the linux community. in fact they are ANTI-FLOSS

who knows the reason he use linux at all... people like this should use windows and be happy with nvidia closed source drivers.

but use linux like this moron is really full stupid mode. if you REALLY want to use linux: BUY AMD HARDWARE

if you want closed source buy nvidia and use windows.

[oiaohm]

This "advantage" also means you cannot create compositor-independent utilities implementing e.g. screen recording or casting.

That is not true with open source graphics drivers.

https://obsproject.com/forum/threads/experimental-zero-copy-screen-capture-on-linux.101262/

This obs experiment using libdrm does not care what wayland compositor or X11 server you have loaded to screen-capture or cast. Yes this experement will libdrm and open source drivers should come possible with closed source Nvidia drivers when Nvidia drivers finally support DMA BUF fully.

If you are wanting to capture a individual window you don't even need that compositor to-do that remember DMA BUF is a file handle you can access a process with enough privileges and get a copy of a file handle.

The reality here birdie is there are a lot compositor neutral tools that can be made. While trolls like you spreading disinformation out there they likely hood of them becoming well developed is low.

Here's another great "advantage": applications running under Wayland compositors are glued to it, so if the compositor crashes, all your apps crash momentarily with it. The funny thing is that it's not the case for X.org, Windows, MacOS where apps will continue to run in case the window manager has stopped working.

Here you go with another lie. If you build X.org on current eglstreams when the X11 server crashed all the X11 applications would go with it. There is a design flaw in eglstreams.

https://bugs.kde.org/show_bug.cgi?id=428089

The reality here is KDE and SWAY compositor do in fact restart while Wayland applications keep on working. Disconnect and reconnect to the compositor is part of libwayland-client this include compositor crash handling where if the compositor restarts quick enough the already running applications just reconnect.

So a well made wayland compositor all you applications don't crash with the compositor in fact even non well made compositor they don't they crash until after the compositor is timed out as gone and not being replaced on the application side. Yes this restarting of wayland compositor or x11 requires you GPU drivers to-do the right things like not killing off buffers it should not so that applications can keep on working to reconnect.

[pal666]

The correct approach would be to acknowledge and address the huge list of issues without the kind of arrogance or bigotism

ok, how many x11 issues you've acknowledged and addresed without arrogance or bigotism?

Until then, we'll have to mention wayland improvements, as they are much needed to reach parity for everyone

to reach parity with wayland x11 needs many improvements which it isn't going to get

[qarium]

birdie:
also birdie troll
what a f*cking moron

yes this man is a Nvidia troll... just ignore him.

[pal666]

Sorry to crap on this parade but when will the stream of "X, Y, Z has improved support for Wayland" end? I thought at least Gnome/Mutter has supported Wayland perfectly for at least a couple of years now. When was the last time you read, "Something has improved support for X.org"? I don't remember such news pieces at all actually.

moron, the only wayland mentioned in article is xwayland, which is x11 server. and improvement was "don't run it unconditionally, run it only when user runs x11 app". which means now enough users aren't using x11 apps at all. sorry that wayland crapped into your pants again

[sarmad]

Anywho, as someone who doesn't use GNOME I thought that Wayland support is pretty much nailed down. Is that true and are they just keeping up with the continued Wayland development, or are there any big issues with GNOME on Wayland that still need to be ironed out like KDE?

I've been using Gnome on Wayland for more than a year and I can say it's mostly nailed down, but there are still minor issues that aren't yet on par with X11. Things I can think of:
- Some issues with drag n drop.
- External monitors connected to eGPU.
- Screen sharing is still lacking. This is mostly an issue with the applications not being updated to use Wayland, but I'm not sure if there is any pieces missing in the implementation itself on Gnome's side.

[intelfx]

Anywho, as someone who doesn't use GNOME I thought that Wayland support is pretty much nailed down. Is that true and are they just keeping up with the continued Wayland development, or are there any big issues with GNOME on Wayland that still need to be ironed out like KDE?

You thought correct. I don't know of any big issues remaining with GNOME on Wayland. But I'd rather not say "keeping up with the continued development of Wayland" per se — I'd rather just call it continued development. As in: fixing bugs, improving performance, conducting architectural reworks, and catering to unusual requirements of other apps (through fixing obscure cases and/or implementing optional features and protocols). Although new protocols may be appearing from time to time in Wayland itself, it doesn't happen often.

[Sethox]

I am using Wayland on Gnome (in Archlinux) as my daily workflow as of right now and I'm in a sweetspot where all the applications I use works well with Wayland or XWayland.
The main applications I use:

• Firefox
• Lutris
• Wine (XWayland) [Wayland support exists both third party and in mainline]
• Thunderbird
• VLC

And with a double screen setup (1080p) when I start playing games on Wine fullscreen on the second screen, Wayland forces Wine to set the application (fullscreen) on the second screen on demand, something it doesn't happen on X11. But my workflow is so small as the list suggest. Just recently started to use Wayland (this month) and Archlinux, very satisfied as of now.

[smitty3268]

Anywho, as someone who doesn't use GNOME I thought that Wayland support is pretty much nailed down. Is that true and are they just keeping up with the continued Wayland development, or are there any big issues with GNOME on Wayland that still need to be ironed out like KDE?

From the release notes, these are the changes related to wayland:

• Consider clients without mapped windows for xwayland auto-shutdown
• Default to starting Xwayland on demand
• xwayland: Restore abstract socket support
• Fix stuck icon in DND operation between X11 and wayland
• xwayland: Set xrandr primary output
• Gracefully handle Xwayland crashes
• wayland: Provide previous window dimensions on restore
• Fix xwayland grabs for override-redirect windows

Seems like mostly XWayland integration issues. The restore window dimensions one seems like the most important one in terms of user experience.