search

mate-desktop / mate-wayland-session

GNU General Public License v2.0
31 stars 5 forks source link

Cannot login to mate wayland #20

Open realzendroid opened 1 month ago

realzendroid commented 1 month ago

On my debian 12 installation, When logging in and selecting Mate on wayland, My screen goes black for a second and goes back to the login screen, I also have wayfire with plank setup as an option and that works, I am using sddm

lukefromdc commented 1 month ago

This requires wayfire itself to crash, wonder if something went wrong with the initial configuration file creation? Try renaming ~/.config/mate/wayfire.ini and try it again.

You may need to also rename your ~/.config/wayfire.ini file as you might have something in it conflicting with the mate wayfire session. If so, you will need to delete or rename ~/.config/mate/wayfire.ini a second time unless it never got written on the previous attempt to run the session. If that file does not exist after an attempt to run the session, something is crashing mate-wayland.sh but note that that doesn't call anything you are unlikely to have installed.

You mention Plank which I have not tried, you could be getting a conflict, so move that default wayfire config file, try again to start (and thus autoconfigure) the mate-wayland session, and if it works you can move that default wayfire.ini file in ~/.config (NOT the one in ~/.config/mate) back for the Plank session.

If you do not have firedecor installed (which is intended to be optional), install it, if this fixes the problem we are getting a crash instead of nonuse of it when it is not present, and that's a bug. The sed call in mate-wayland.sh is supposed to limited to cases where firedecor is installed by the check for existance of the binary.

If that still fails, run systemctl stop sddm and change VT's to any VT that gives you a prompt, then run mate-wayland.sh and see what error messages come up if the session does not start. If you get an error in the script that can be fixed here, if you get a problem in wayfire it might be a crashing plugin since you can run it at all. In that case we need to know which one it is. if something cannot autostart it should just silently fail, not take down the compositor so it's unlikely the problem is in mate-wayland-components.sh but if it is running mate-wayland.sh from console should show it.