Replies: 3 comments 1 reply
-
I think you have it setup mostly correctly since it's working. Whatever is changing the session doesn't seem to be doing it smoothly. Would it help if you started wayfire on a different tty than the greeter? |
Beta Was this translation helpful? Give feedback.
-
I have faced this issue at various stages. I believe this issue was raised with wlroots as well. In the meanwhile, this is what I have come up with:
(I remember some discussion in wlroots regarding this transition from dm-wlroots-compositor to user-wlroots-compositor. Something related to sending blank frames to drm or similar, which would result in a smooth transition. But I have never seen a smooth transition with wayfire) |
Beta Was this translation helpful? Give feedback.
-
@marcusbritanicus Thank you for such a clear answer, this is very helpful. |
Beta Was this translation helpful? Give feedback.
-
Hi All
I am on my void-linux musl(because I like challenges or am stupid) on an ARM64 chromebook.
Not sure i understand how to use the greeter or how to start it.
I am using regreet.
I did the greetd configuration
the command is "wayfire -c path_to_config"
user greeter -> this always seems silly to me.
And in the wayfire config:
the plugin is autostart
in
[autostart]
regreet=regreet -c /etc/greetd/regreet.toml
autostart_wf_shell=false
It will bring up wayfire with regreet - then I login, it closes the session and opens it with the correct user.
And doing this goes from tty at boot to wayland graphical mode to regreet to tty issuing some logging back to the user session I logged in with.
It is ugly to do it this way.
All graphical greeters require a wayland server to start up so they can work.
So I don't know how to do this
Beta Was this translation helpful? Give feedback.
All reactions