Just wanted to share with you that MATE developers seem to be working on Wayland session!
6 Likes
Wow! Quite impressive to see that wayfire gets adopted as wayland compositor for MATE 
And since the mate developers AFAIK also work, or have worked, with the developers of 'Mir', it seems that if we're very lucky we might have the opportunity to choose between two wayland supporting backends:
- 'Mir' which already got the wayland protocol implemented
- 'Wayfire' (the wayland capable spiritual successor to compiz)
This makes my day 
4 Likes
From what the devs have said you would be able to use any wayland compositor that uses wl roots so wayfire, mir, sway, whatever you want just like with x11 and changing out window managers
4 Likes
Wow this made my day. I hope somebody will work on a CCSM for wayfire. Can't wait for some spinning cube shenanigans under wayland on my MATE desktop.
5 Likes
Awesome stuff guys 
2 Likes
LOL, the first thing I do is shut all that junk, eye candy stuff down. To each his own, which is why I love Linux, choice.
6 Likes
Looking at this statusreport feels so good 
6 Likes
I just came here to post this update!
Wayland is nearly here... So exciting.
6 Likes
In that case I would probably choose for something minimal as Labwc, a kind of OpenBox or Marco replacement for wayland. Here is a screenshot somebody made, that resembles pretty much what I seek in a desktop.
(picture by Jack Dostoevsky published on reddit unixporn)
So cool to have a replacement for both Compiz(Wayfire) and Marco(LabWC)
1 Like
Gonna bump this topic. It's August now. Any updates about Wayland support?
No, according to the straight-to-the-developers link I shared in a few posts earlier, there has been no news since.
2 Likes
So ... when Wayland is fully implemented in MATE, the windows and animations will be much more smoother and all that, yes? I feel like I'm asking a question I already know the answer to, but I'm just looking for confirmation. Thanks.
1 Like
This would theoretically be the case indeed
2 Likes
I don't use compositing (or is that a "yet" ), but ...
This answer (Feb 2023) was provided on AskUbuntu.
The first of the two additional references provided in that posting, specifically making Wayfire functional on Ubuntu seems like it was a clean process (specifically at ubuntu 20.04) and the author's blog shows no hints of any issues in any postings between that and his most recent dated Aug 7, 2024.
The second makes reference to Peux-wayfire-22 (described as Peux OS Wayfire year 2022 dotfiles). Peux-OS is Arch-based. For those more adventurous than myself, there is the ArchCraft page on Wayfire, which offers quite a few details that might be helpful. There is no reference found to Wayfire on the ArchLinux site itself.
There is also a reference to installation scripts on the WayfireWM GitHub itself.
1 Like
@Entomologo, @tkn, @ironfoot, @vkareh,
Can anyone explain the discrepancy between the "Wayland and Meson status page, and the somewhat unsettling tone of the discussion at mate-desktop / mate-wayland-session** which , presumably, is main channel for discussion on the efforts and rollout activities ?
I see that each of Arch, Debian or Ubuntu is not listed as a project using Meson. However, I do see Cinnamon, Elementary, GNOME, GTK+, Waylan, Weston and Xorg listed, which is an encouraging sign that it is the way to go to stay "in sync" with what I view are complementary "peer" organizations to UbuntuMATE.
Not really a discrepancy, it's apples and oranges. AFAIK Meson, the buildsystem, is often used in wayland related projects so it makes sense to use it, but it is not a 'hard dependency' or the like if you want to get things to work.
Also, porting a project over to a different build system can be a hassle. I can imagine that several projects probably want to tweak other things in their project first before making the jump.
Nah, not really unsettling.
These are the kind of healthy discussions that are quite normal in the implementation/installation phase. Which probably means that
- functionally it's pretty much finished.
- it's mainly make/options/install bugzapping from here.
- it is not in an alpha state yet.
- the mentioned problems are probably related to the parts that are not yet on meson but well in the process to get there,
As far as I followed the linked discussion, it is all about the installer and some configscripts. It is unavoidable that there are some installation- and distro-dependent implementation questions. Nothing out of the ordinary here.
Why should that matter ?
3 Likes