HI! Last week-end I upgraded my laptop with MATE 20.04 to 22.04. Everything was easy and enough fast, no problems at all.
Just a question: I understand that Wayland is the default for Mate 22.04, I made an automatic upgrade
do-release-upgrade from 20.04 with X11, do I have Mate 22.04 with Wayland now?
Is it possible to verify it? Actually in
top I can see XORG process.
I use often Zoom and I red that Wayland is not full compatible with Zoom: is it possible to switch back to X11 if Zoom has serious problems?
HI! Last week-end I upgraded my laptop with MATE 20.04 to 22.04. Everything was easy and enough fast, no problems at all.
actually it says
So I'm not using Wayland, I'd like to try it. I see in login screen that I can choose different options, but no one of those works properly, the only option working is "MATE".
Interesting! I'm running 22.04 on Live USB. $XDG_SESSION_TYPE also shows x11.
I did not understand this to be a fact. Quite cool if true though. Could you point me to where you found this information so I can read up on it? Thanks!
Hi, @smurf (Luca DG).
I'm afraid that is definitely NOT true as @Wimpy (Martin Wimpress) himself wrote the following, on the 21st April 2022:
Ok, I apologize, I red many threads surfing the net and may be I got confused.
Yeah, it's confusing. It's been confusing for years.
Most likely what you read is that stock Ubuntu (the version with the GNOME desktop) has switched to Wayland in 22.04. What stock Ubuntu does is not necessarily indicative of what Ubuntu MATE does. Like @ricmarques said above (actually what @Wimpy said in the 22.04 release notes), the MATE session as it stands cannot run on Wayland without some semi-unofficial "patches". @wmww is the main developer who pushes MATE development regarding Wayland forward, and he's got a number of modified MATE programs that, when used in conjunction with most of the normal MATE applications (which individually support Wayland now), can be used to start a Wayland-based MATE session. I've never tried it myself, but I hear it mostly works. (Should you try it, beware. As with any "beta-quality" software, it's possible it'll crash upon you spontaneously.)
As for the stock Ubuntu side of things, that's confusing because Ubuntu has switched back-and-forth between X11 and Wayland several times since 2017 (if I recall correctly). The following timeline is according to my own (flawed) memory:
- Ubuntu first deployed Wayland as an option when you log in, but not the default, in version 17.10.
- In 18.04 the option was not even included by default.
- In 18.10 the Wayland option was included again, and I think it was even the default.
- But users complained that applications didn't always work right under Wayland, and the cursed Nvidia drivers were unavailable for Wayland (as if you'd actually want them anyway ). So Ubuntu switched back to X11 by default but kept Wayland as an option for the 19.04 and 19.10 releases.
- 20.04 didn't even have Wayland as an option.
- I know for sure that 21.10 didn't have Wayland as even an option, because I was quality assurance testing Ubuntu MATE during that release cycle and I was trying to figure out why Ubuntu MATE's installer had so much trouble communicating with the screen reader. (I had to dig pretty deep to find the answer to that one -- I initially thought it was a difference between Ubuntu using Wayland and Ubuntu MATE using X11, but I figured out that both used X11.)
And, if you believe this article from gHacks (https://www.ghacks.net/2022/04/21/ubuntu-22-04-lts-with-gnome-42-and-wayland-as-the-default/), Wayland is the default on stock Ubuntu now, and it looks like it's the first LTS release to hold that achievement.
However, let me make this clear: Officially, without extra patches, the whole MATE desktop doesn't run on Wayland yet. I know that because I'm a member of the MATE development team. Sorry.
OK, enough of my diatribe for one post.
Please, I don't want to start a fire. I apologize again for my mistake.
Not to worry, you didn't start the fire. This is a pain point that has existed for a while now and the developers are doing what they can to resolve it. That doesn't make people less frustrated or less eager for the upgrade when it becomes available.
Yeah, nobody starts fires around here. This is probably the most civilized community I've been a member in. All I wanted to do was clarify the Wayland / X11 issue further -- nothing else. Sorry it rubbed off wrong.
This is probably the most civilized community I've been a member in.
I definitively agree.
That's perfectly normal. No worries and you don't have anything to apologize for
If my previous terse reply in this topic came off as if I was criticizing you in any way, please rest assured that was not the case and I apologize for not having made that clear in that reply of mine.
Yes that's what I understand, that Wayland is not quite ready for MATE flavour of Ubuntu.
Does anyone know what the time line will be for Wayland on MATE? After 22.10?
I guess I need to be the killjoy reminding everyone that Wayland is not even remotely close to being functional for any non-toy/demo scenario, other than via XWayland.
The list of software that not only "doesn't currently", but "will never" work on Wayland is rather large, because of mistakes made 15+ years ago when Wayland was new. Among other things, this has led to a chicken and egg situation where nobody wants to waste time rewriting their code for Wayland when they gain nothing from doing so; and users can't have "full" Wayland desktops because nobody wants to port their code to it for no reason.
That "15+ years" isn't a typo - that's how long Wayland has been "nearly ready". (It's a bit like fusion power and flying cars... :P). Ubuntu's Mir project was started, completed, and abandoned in less than half that time, and was still about as successful as Wayland has been so far.
Some projects will eventually move to "Wayland native" versions, simply because bored developers like to play with New Toys. MATE will doubtless be one of those projects someday, but even if that were to happen tomorrow, it would still be years at best before all the software you wanted to run was also migrated - so you'll be running some form of X for a very, very long time yet.
There's nothing wrong with looking forward to the day Wayland might be usable, but there's also no reason at all to get excited over it. Even if/when it does happen, the best you can hope for is that - from your perspective as a user - nothing seems to have changed at all.
It's easy to say that but time still marches on and while things never quite move as fast as we want them to things do eventually change. I remember when Canonical decided we were going to ditch ALSA for PulseAudio and forced the change on everyone things were a mess and there was HOWTO after HOWTO on how to revert to ALSA or to fix PulseAudio or switch from both to OpenSound, etc etc. And yet here we are today most of us with a working PulseAudio setup, about to replace it with PipeWire... The more things change...
But seriously, I am mostly happy with X11. I can do pretty much everything I care about using it and have been getting decent performance with it for my purposes. The one thing that I care about Wayland for is getting the ability to run Android apps and games on my system transparently and not needing to have or show the entire Android system in a window.
AnBox is basically dead at this point--what there is is either broken and out of date to the point of worthlessness. The image you're supposed to use is worthless because it has major audio and video codec errors that the developer simply ignores. WayDroid is the heralded successor that is in active development and which apparently functions well but that does not actually run well on X11...there is apparently a way to work around this with Weston but then you're stuck emulating an entire screen and displaying everything in a window instead of transparently.
So there actually are use cases for this beyond just being a 'toy' and it gets frustrating when people simply pretend there aren't. I understand there are good, practical reasons why we do not yet have Mate on Wayland, but please don't pretend there is no use for it or that no one wants it. We do have use for it and we do want it.
(edited to remove some poor phrasing and jackassery. My apologies to bornagainpenguin).
The problem is that for every new piece of Wayland-only software, there are multiple pieces of X-only software that will no longer work properly, much of which is no longer actively in development because it was finished years ago and the authors have moved on.
You've found one of the former that's important to you, but there's a lot of weight on the other side of the scale - anyone who depends on working RandR support for VMs, or screen capture, or remoting, to name just three. That affects a much larger group of people (VM use alone greatly outnumbers bare-metal Linux installs last time I looked) so it's not as simple as just "MATE moves to Wayland, and everybody's happy", even if you dismiss the enormous amount of work involved in doing that - and the fact that it's a moving target on top of that because Wayland still isn't finished.
(ed: XWayland is covered in a later post).
Wayland is now one of the longest-running jokes in the entire history of software development. It's badly designed, the implementation has been a farce, and the project has been mismanaged to a staggering extent. All three of those things are still ongoing, and if you expect any of them to change after 15 years I've got an Einstein quote for you.
That long history includes a lot of unethical and dishonest behavior on the part of the two corporations pushing Wayland, and a lot of hostility and arrogance from some members of the project towards the Linux community as a whole; and especially, any developers who don't work for one of those corporations.
All Wayland does, and all it has ever done, is stake out a claim to get in the way of any number of better options. If it had shipped on time, the current discussion would be about replacing it with Arcan or something similar - much like your PulseAudio example with PipeWire now superceding it.
Since Wayland still isn't even at the Beta stage though in reality, paying attention to it now only doubles down on the harm it's already done, because you're asking people to waste their time rewriting code for it just to either have to do so again in a few more years, or be contributing to entrenching a pile of mediocrity for another 15 years because nobody wants to have to deal with an invasive rewrite a second time.
Neither of those outcomes is at all desirable to most developers, or at all beneficial to most users. We're going to end up there, obviously, since two very large corporations are dead set on it, but that doesn't make it any less of a bad result. By the time it dies the death it deserves, Wayland will have wasted millions of hours of irreplaceable developer and user time, for no reason and to no benefit.
That's why I'm opposed to it - and your complaint with AnBox -> WayDroid is exactly that scenario playing out..
You may have one or two valid points in your rant, but please tone it down a bit.
@bornagainpenguin doesn't deserve abuse or a condescending stance just for his opinion.
Also , he has several valid points too.
Listen to what Daniel Stone, one of the developers of X11, has to say about X11 vs Wayland
Very interesting. I had no idea X was so complex.
It's entirely possible I misjudged your post and completely misunderstood it. I don't pretend to have a perfect understanding of anything. I'm just happy when my computer which ever one I am using looks and behaves the way I want it to and is capable of doing what I ask of it.
Lately I've wanted to run Android applications transparently on Linux. I remember when Canonical first announced they were working on it. I understood it wouldn't be something we'd see right away so I resolved to be patient about it. That was almost a decade ago. Eventually I found AnBox but as I said it's basically been bitrotting for the past several years. Then word came of a fork that was being actively developed and required Wayland to work.
Was I disappointed? Sure, but as far as I can tell it needs Wayland in order to display just the application and not the whole system. Is that absolutely true? How would I know? I'm not a programmer. I don't know of anything else that is trying to tackle the problem of making it work on Linux though. Meanwhile (and I hate to use Microsoft as a comparison for anything) Windows 11 seems to have support for doing this. ChromeOS has support for doing this. Why don't I just bugger off and use either of those then? Because I like the Mate desktop too much to give it up.
I'm sorry if I spoiled your rant against Wayland's existence. I do have what I consider a valid use case though and I dislike that being summarily rejected as being just a 'toy' so I took it harder than perhaps I should have. I wasn't trying to stomp on your toes though, just pointing out that there have been changes like this before and that while they can be messy as hell and take a while to make happen, they do eventually take place. I was basically reaffirming the desire I have to see my ability to run Android apps transparently on Linux using my preferred desktop while saying also that I am willing to be as patient as it takes. Hell I've been waiting almost ten years, what's a few more years?
If you have proof that Wayland isn't actually necessary, I'm all ears. If you know a way to do this without waiting on Waydroid, again I'm all ears. But please don't just dismiss anyone waiting patiently as someone who just wants to play with a toy. I'm just one person with a particular desire to do something that seems to require Wayland. I'm sure there are other people with their own reasons to use it. I suspect as rollout continues to happen there will be other uses that neither of us can think of right now.
Incidentally despite how far off topic we seem to have drifted, you mentioned that Wayland is stealing time away from better options. Would you care to mention some of those so we can see what they are?
EDIT: Since the thread has been locked for new replies over the weekend when I was busy I was not able to reply. Arcan is exactly the name that came to me when you mentioned alternatives, and I was wondering if it or some other system being worked on was what you were thinking of. Thanks, for the reply and I'm glad to see that despite your frustration over the way things have been going with Wayland that we did not in fact step on each others toes and were able to have a discussion.