Butterknife 0.1.7 — argon2id LUKS, polished login screen, Ly works on Debian

Butterbian
1

Butterknife 0.1.7 is out. This is a meatier release than the recent patch bumps — a few things that have been nagging at the install experience finally got cleared up.

Stronger encryption by default

LUKS-encrypted installs now use argon2id as the KDF instead of pbkdf2 — the modern memory-hard variant, significantly more resistant to offline brute force on stolen disks. If you’ve been on the fence about encrypted installs, this is the version where it stops being a compromise. Existing encrypted installs are unaffected; only new installs get the change.

The login screen actually looks like Butterbian

lightdm-gtk-greeter is now wired up with an optional Butterbian theme — dark wireframe wallpaper, Adwaita-dark form, the Butterbian logo as the default user avatar. The installer asks before applying; decline and you get stock lightdm-gtk-greeter. Tweak it after the fact via lightdm-gtk-greeter-settings (GUI, no config file editing).

Ly actually works on Debian

This one was overdue. Previously, picking Ly from the display-manager menu installed the package but didn’t register it as the system DM — Debian ships Ly as a systemd template, not a static service, so the standard “enable ly.service” approach fails silently. Now it’s correctly wired up: Ly takes over tty2 at boot. If you’ve wanted a TUI greeter, this is the version.

Across the WM setup repos

The X11 setup scripts (awesomewm, bspwm, dwm, i3, openbox, qtile) switched from lxappearance to nwg-look for GTK theme/icon picking — matching the sway / swayfx pair. One picker everywhere, X11 and Wayland.

Bug fixes

  • Installer no longer crashes after a successful install when wm-chooser cleans up its own sudoers file.
  • wm-chooser self-cleans the temporary NOPASSWD sudoers entry on exit, closing a window where a power loss during WM picking could leave passwordless sudo on the new system.

Known issue — sway in VMs

If you’re testing sway in VirtualBox / QEMU / VMware with a Wayland session, you may see cursor offset (visual cursor drifts from the actual click position). This is a wlroots+VM hardware-cursor mismatch, not a
butterknife bug. Workaround:

  mkdir -p ~/.config/environment.d
  echo 'WLR_NO_HARDWARE_CURSORS=1' > ~/.config/environment.d/wlroots.conf

Then log out and back in. Bare metal is fine; this only affects VM testing.

Get it

If you install it, let me know how it goes — especially if something breaks. Bug reports here or on Codeberg.

1 Like