-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot login to mate wayland #20
Comments
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.
|
The same here. Debian 12. |
First, make sure you have wayfire installed. If you do, the package should include
/usr/share/doc/wayfire/examples/wayfire.ini which is where the session looks for
the default configuration file if wayfire has never been run before. Make sure that
file exists. If it does not for any reason and you don't have a ~/.config/wayfire.ini
file either, than the session does not have a default configuration file to modify.
That modification at first run is where ~/.config/mate/wayfire.ini comes from
With the problem you report wayfire itself should not be able to run. Once you get a
default wayfire session to run once, you should have ~/.config/wayfire.ini which the
session looks for first to keep a user's wayfire customizations intact.
If you have wayfire installed without the examples, you might need a -doc package
for wayfire if your distro strips out /usr/share/doc/wayfire/examples. Debian Unstable
does not seem to do this, I have that file in at least one wayfire 0.9 package provided
by Debian.
What exact package version for wayfire do you have installed?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: