Closed lukefromdc closed 10 months ago
I am using the normal wayfire session from fedora repos and mate-volume-control is visible in mcc window and menus.
Also MATE is registrated for OnlyShowIn
at freedesktop.org.
I am still wondering how this can be work without a new registration?
desktop-file-utils needs to know about the session.
In the absence of a new registration, this is probably working because nothing outside of MATE is looking for the OnlyShowIn values while in that mate session.
Thus, we probably do need to close all of these, and in mate-wayland session change the session name simply to MATE and apply the default MATE settings in the gsettings override file to MATE instead of MATE-wayland. That would just mean that the MATE defaults would be applied to anything reading the GNOME values for gtk theme, icon theme, overlay scrolling, and button layout in both wayland and x11 MATE sessions. The x11 session does not read these values from GNOME gsettings preferences but rather the MATE prefs so this should have no effect outside the MATE on wayland session
Just pushed https://github.com/mate-desktop/mate-wayland-session/commit/3a262255213695a34e35c69ce0711d91d5d7a632 to use XDG_CURRENT_DESKTOP=MATE so we can close all of these
Note that if you'd rather avoid using a gsettings file to use MATE rather than GNOME defaults on a new install (and thus use whatever GNOME defaults to), I am entirely OK with removing it, but I am working under the assumption that on a new install, the MATE wayland session should look and feel as much like the x11 session as is possible.
Compositors default to GNOME for this probably as the GNOME schemas will be present if dconf and gsettings are installed. If we don't want to deal with that we can either fork a compositor (lots of extra maintainance), or work with the devs at wayfire (or any other wlroots compositor) to get a runtime option to use MATE gsettings values in the compositor.
This importance of this is in the fact that in wayland, the work of an xsettings manager (part of m-s-d for instance) is done by the compositor itself.
........and apply the default MATE settings in the gsettings override file to MATE instead of MATE-wayland.
I don't get what you mean. Why a gsettings override file? Do you use a gsettings override file in mate-wayland-session repositority?
Compositors default to GNOME for this probably as the GNOME schemas will be present if dconf and gsettings are installed. If we don't want to deal with that we can either fork a compositor (lots of extra maintainance), or work with the devs at wayfire (or any other wlroots compositor) to get a runtime option to use MATE gsettings values in the compositor.
+1 for a Mate integration in wayfire. I recall that in old compiz-0.88 repo the gnome part was forked to mate. I am guessing that wayfire devs use the origin gnome session part when the adopt wayfire from compiz.
Yes, the gsettings override to default to MATE defaults is in mate-wayland-session/data
We can keep it or ditch it pending integration w wayfire that would remove the need for it.
Use
OnlyShowIn=MATE;MATE-wayland;
instead ofOnlyShowIn=MATE;
in the .desktop file so mate-control-center can show the capplet same as in x11. It works in both sessions