Greetd: Difference between revisions
imported>Equirosa m fix small typo |
mNo edit summary |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
swayConfig = pkgs.writeText "greetd-sway-config" '' | swayConfig = pkgs.writeText "greetd-sway-config" '' | ||
# `-l` activates layer-shell mode. Notice that `swaymsg exit` will run after gtkgreet. | # `-l` activates layer-shell mode. Notice that `swaymsg exit` will run after gtkgreet. | ||
exec "${pkgs.greetd.gtkgreet}/bin/gtkgreet -l | exec "${pkgs.greetd.gtkgreet}/bin/gtkgreet -l; swaymsg exit" | ||
bindsym Mod4+shift+e exec swaynag \ | bindsym Mod4+shift+e exec swaynag \ | ||
-t warning \ | -t warning \ | ||
| Line 52: | Line 52: | ||
<code>initial_session</code> is executed automatically. If you just define <code>default_session</code>, greetd will ask for a password and execute <code>command</code> with user <code>myuser</code>. | <code>initial_session</code> is executed automatically. If you just define <code>default_session</code>, greetd will ask for a password and execute <code>command</code> with user <code>myuser</code>. | ||
{{note|1=<nowiki/> | |||
If you're hosting gtkgreet in a Wayland compositor, there is a known issue, between GTK portals and dbus, of a delay before the greeter appears,. There are a couple known workarounds depending on the compositor you're using: | |||
* Cage: https://github.com/Hjdskes/cage/issues/169#issuecomment-691659377 | |||
* Sway: https://github.com/swaywm/sway/wiki#gtk-applications-take-20-seconds-to-start | |||
}} | |||
[[Category:Desktop environment]] | |||