Vladimir Kostelei
c6c40dbced
* lock: keep the fingerprint reader usable across suspend
The reader stopped responding after the lid was closed and opened, after a long
idle period, and after suspend.
The shell held a PAM session for as long as the screen was locked, so a suspend
always landed on a running verify. fprintd then suspends the device under the
verify, pam_fprintd's ReleaseDevice fails with "device is still busy", and the
claim is never released, so every later Claim fails until fprintd restarts. The
reader is now released when the monitors blank and armed again when they come
back, so a suspend has nothing left to wedge.
The PAM profile drops to max-tries=1 and sets an explicit timeout. pam_fprintd
only counts a wrong finger, so one finished session is now one wrong scan and
maxFprintTries means the number of scans it names rather than five times that.
A timeout expiry arrives as PamResult.Error, exactly like a device fault, so a
session that ran at least as long as the configured timeout is treated as a
planned renewal instead of spending the error budget and painting an error.
A suspend that still lands while the screen is on wedges as before. Recovery now
waits out fprintd's idle timeout instead of climbing to it, which brings the
reader back about 37 seconds after resume instead of about 98.
SessionService gains lidOpened from UPower, because logind can ignore the lid on
AC and resume alone is not enough. The lock PAM state machine is fixed alongside:
PamResult.Failed was dropped, a pending retry outlived the contexts that owned
it, and an availability check reset the wrong-scan counter.
* lock: time the fingerprint session from the verify, not the claim
pam_fprintd's timeout runs from the verify, but the session age was measured
from start(), which folds the claim into it. A slow claim plus a verify that
failed before its own timeout could add up past the timeout and be taken for a
planned renewal, skipping the backoff. A session that never reached a verify had
the same problem.
The age now starts at the message pam_fprintd sends when the verify begins, so a
session that never verified can never qualify as an expiry, and a slow claim no
longer ages a fault. The message is translated and quickshell clears it before
completed, so only its timing is used, never its text.
That message arrives after pam_fprintd has already armed its deadline, because
VerifyStart is asynchronous, so the age read here runs short of the real timeout
and a slack makes it up. The bias is deliberate. A fault misread as a timeout
costs one extra retry, while a timeout misread as a fault parks the reader behind
a backoff that grows to a minute, which on an idle lock screen would leave it
unusable most of the time.
Also corrects the comment that claimed a timeout is reported without a message.
---------
(cherry picked from commit d7074a53eb)
DMS Backend & CLI
Go-based backend for DankMaterialShell providing system integration, IPC, and installation tools.
See root README for project overview and installation.
Components
dms CLI Command-line interface and daemon for shell management and system control.
dankinstall Distribution-aware installer for deploying DMS and compositor configurations on Arch, Fedora, Debian, Ubuntu, openSUSE, Gentoo, and Void. Supports both an interactive TUI and a headless (unattended) mode via CLI flags.
System Integration
Wayland Protocols (Client)
All Wayland protocols are consumed as a client - connecting to the compositor.
| Protocol | Purpose |
|---|---|
wlr-gamma-control-unstable-v1 |
Night mode color temperature control |
wlr-screencopy-unstable-v1 |
Screen capture for color picker/screenshot |
wlr-layer-shell-unstable-v1 |
Overlay surfaces for color picker UI/screenshot |
wlr-output-management-unstable-v1 |
Display configuration |
wlr-output-power-management-unstable-v1 |
DPMS on/off CLI |
wp-viewporter |
Fractional scaling support (color picker/screenshot UIs) |
keyboard-shortcuts-inhibit-unstable-v1 |
Inhibit compositor shortcuts during color picker/screenshot |
ext-data-control-v1 |
Clipboard history and persistence |
ext-workspace-v1 |
Workspace integration |
dwl-ipc-unstable-v2 |
dwl/MangoWC IPC for tags, outputs, etc. |
DBus Interfaces
Client (consuming external services):
| Interface | Purpose |
|---|---|
org.bluez |
Bluetooth management with pairing agent |
org.freedesktop.NetworkManager |
Network management |
net.connman.iwd |
iwd Wi-Fi backend |
org.freedesktop.network1 |
systemd-networkd integration |
org.freedesktop.login1 |
Session control, sleep inhibitors, brightness |
org.freedesktop.Accounts |
User account information |
org.freedesktop.portal.Desktop |
Desktop appearance settings (color scheme) |
| CUPS via IPP + D-Bus | Printer management with job notifications |
Server (implementing interfaces):
| Interface | Purpose |
|---|---|
org.freedesktop.ScreenSaver |
Screensaver inhibit for video playback |
Custom IPC via unix socket (JSON API) for shell communication.
Hardware Control
| Subsystem | Method | Purpose |
|---|---|---|
| DDC/CI | I2C direct | External monitor brightness |
| Backlight | logind or sysfs | Internal display brightness |
| evdev | /dev/input/event* |
Keyboard state (caps lock LED) |
| udev | netlink monitor | Backlight device updates (for OSD) |
Plugin System
- Plugin registry integration
- Plugin lifecycle management
- Settings persistence
CLI Commands
dms run [-d]- Start shell (optionally as daemon)dms restart/dms kill- Manage running processesdms ipc <command>- Send IPC commands (toggle launcher, notifications, etc.)dms plugins [install|browse|search|lock|restore]- Plugin management and portable exact-revision lockfilesdms brightness [list|set]- Control display/monitor brightnessdms color pick- Native color picker (see below)dms update- Update DMS and dependencies (disabled in distro packages)dms greeter- Deprecated; forwards to the standalone dms-greeter binary
Color Picker
Native Wayland color picker with magnifier, no external dependencies. Supports HiDPI and fractional scaling.
dms color pick # Pick color, output hex
dms color pick --rgb # Output as RGB (255 128 64)
dms color pick --hsv # Output as HSV (24 75% 100%)
dms color pick --json # Output all formats as JSON
dms color pick -a # Auto-copy to clipboard
The on-screen preview displays the selected format. JSON output includes hex, RGB, HSL, HSV, and CMYK values.
Building
Requires Go 1.25+
Development build:
make # Build dms CLI
make dankinstall # Build installer
make test # Run tests
Distribution build:
make dist # Build without update features
Produces bin/dms-linux-amd64 and bin/dms-linux-arm64
Installation:
sudo make install # Install to /usr/local/bin/dms
Development
Setup pre-commit hooks:
git config core.hooksPath .githooks
This runs gofmt, golangci-lint, tests, and builds before each commit when core/ files are staged.
Regenerating Wayland Protocol Bindings:
Protocol XML files live in internal/proto/xml/. Bindings are generated with the dankgo go-wayland-scanner:
go run github.com/AvengeMedia/dankgo/cmd/go-wayland-scanner@latest \
-i internal/proto/xml/wlr-gamma-control-unstable-v1.xml \
-pkg wlr_gamma_control -o internal/proto/wlr_gamma_control/gamma_control.go
Module Structure:
cmd/- Binary entrypoints (dms, dankinstall)internal/distros/- Distribution-specific installation logicinternal/proto/- Wayland protocol bindingspkg/- Shared packages
Installation via dankinstall
Interactive (TUI):
curl -fsSL https://install.danklinux.com | sh
Headless (unattended):
Headless mode requires cached credentials or a passwordless rule for your privilege escalation tool (sudo, doas, or run0). With sudo, run sudo -v first:
sudo -v && curl -fsSL https://install.danklinux.com | sh -s -- -c niri -t ghostty -y
sudo -v && curl -fsSL https://install.danklinux.com | sh -s -- -c hyprland -t kitty --dms-greeter -y
sudo -v && curl -fsSL https://install.danklinux.com | sh -s -- -c niri -t ghostty --git-deps niri,quickshell --all-features -y
| Flag | Short | Description |
|---|---|---|
--compositor <niri|hyprland|mango> |
-c |
Compositor/WM to install (required for headless) |
--term <ghostty|kitty|alacritty> |
-t |
Terminal emulator (required for headless) |
--privesc <sudo|doas|run0> |
Privilege escalation tool (default: autodetect) | |
--git |
Install the git version of every dependency that has one | |
--git-deps <name,...> |
Install the git version of specific dependencies (e.g. niri,quickshell) |
|
--all-features |
Enable all optional dependencies (dms-greeter, danksearch, dankcalendar) |
|
--dms-greeter |
Install dms-greeter | |
--danksearch |
Install danksearch and enable its user indexing service | |
--dankcalendar |
Install dankcalendar | |
--include-deps <name,...> |
Enable optional dependencies (e.g. dms-greeter) |
|
--exclude-deps <name,...> |
Skip specific dependencies | |
--replace-configs <name,...> |
Replace specific configuration files (mutually exclusive with --replace-configs-all) |
|
--replace-configs-all |
Replace all configuration files (mutually exclusive with --replace-configs) |
|
--yes |
-y |
Required for headless mode - confirms installation without interactive prompts |
Headless mode requires --yes to proceed; without it, the installer exits with an error.
Configuration files are not replaced by default unless --replace-configs or --replace-configs-all is specified.
Optional packages (dms-greeter, danksearch, dankcalendar) are disabled by default; enable them with their dedicated flags, --include-deps, or --all-features.
When no flags are provided, dankinstall launches the interactive TUI.
Headless mode validation rules
Headless mode activates when --compositor or --term is provided.
- Both
--compositorand--termare required; providing only one results in an error. - Headless-only flags (
--privesc,--git,--git-deps,--all-features,--include-deps,--exclude-deps,--replace-configs,--replace-configs-all,--yes,--danksearch,--dankcalendar,--dms-greeter) are rejected in TUI mode. - Positional arguments are not accepted.
Log file location
dankinstall writes logs to /tmp by default.
Set the DANKINSTALL_LOG_DIR environment variable to override the log directory.
Supported Distributions
Arch, Fedora, Debian, Ubuntu, openSUSE, Gentoo, Void (and derivatives)
Arch Linux
Uses pacman for system packages, builds AUR packages via makepkg, no AUR helper dependency.
Fedora
Uses COPR repositories (avengemedia/danklinux, avengemedia/dms).
Ubuntu Requires PPA support. Most packages built from source (slow first install).
Debian Debian 13+ (Trixie), testing, and sid. Stable quickshell from Debian (trixie-backports on 13). Other companions via OBS.
openSUSE Most packages available in standard repos. Minimal building required.
Gentoo Uses Portage with GURU overlay. Automatically configures USE flags. Variable success depending on system configuration.
Void Linux Uses XBPS with the DMS and DankLinux self-hosted repositories.
See installer output for distribution-specific details during installation.