asrifox / iced-greet

greetd greeter made with iced

iced-greet

Graphical greeter for greetd made with iced

Features

• Input username directly or select from the list (queries /etc/passwd)
• Launch any program on authentification
  • Select from your Xorg (/usr/share/xsessions) or Wayland (/usr/share/wayland-sessions) sessions
  • Select from the predefined list in /etc/greetd/environments
  • Or input the command directly
• Shutdown (SD) or restart (RE)
• User avatars
  • Put images named {username}.png in /etc/greetd/faces/ (e.g. /etc/greetd/faces/asrifox.png)

Planned

• Configuration/theming
• User avatar in a circle

Install

1. Install greetd
2. Build iced-greet (e.g. cargo build --release)
3. Copy the executable to the global PATH location (e.g. sudo cp target/release/iced-greet /usr/local/bin/)
4. Install a Wayland compositor, such as cage or sway
5. Edit /etc/greetd/config.toml to set the new greeter:

...
[default_session]
command = "cage -s -- iced-greet"
user = "greeter"

Read greetd manual for more clarification.

Troubleshooting

Graphics drivers

iced-greet is confirmed to work in cage on an NVIDIA card with nouveau drivers. Proprietary nvidia drivers won't work because cage/sway themselves don't work with them. I have not yet tried any other Wayland compositors nor AMD/Intel devices.

Launch fails

If you see error messages and/or the greeter does not launch, you may be locked out of your system. Try switching to another VT to log in through agetty or something and edit /etc/greetd/config.toml to use the default agreety or any other greeter.

If VT switching fails, greetd manual suggests modifying kernel command line in your bootloader to disable greetd.service, however, I couldn't do it. Instead, I use a LiveUSB with a distro installer to mount the system partition, chroot into it and edit the config.

Development

Testing

To debug/run the application without connecting to greetd socket (which will fail if the user is not in greeter group), use 'test' command line argument (e.g. iced-greet test or cargo run -- test). Note that this is not the same application as the main one, so you will need to copy the desired changes to the ui module before building to install.

Backend

The application uses iced's glow (OpenGL) backend. With wgpu backend the window loads for a very long time. perf results suggest that it has something to do with Vulkan driver allocation for NVIDIA. I plan to test wgpu with an AMD card in the future.