Skip to content

kuma v0.16.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Aug 06:52
v0.16.0
78388d1

Added

  • kuma's own verbs are in your launcher. Eight entries: edit the declaration, show drift, review proposals, system health, check for updates, rebuild, roll back, snapshots. Type kuma into whatever launcher the session shipped and they come back. They are ordinary .desktop files, so there is no plugin to install and nothing to configure, and they are on the COSMIC desktop as well as the niri one.

Each opens a terminal window and holds it open after the verb exits, so output you were meant to read is still there. Press enter to close it.

  • The niri desktop is one shell instead of eight programs. Noctalia draws the bar, notifications, wallpaper, OSDs, idle, lock screen, night light and a control centre that owns wifi, bluetooth, audio and brightness. waybar, mako, fuzzel, wob, swaybg, swayidle, swaylock and wlsunset are gone from the image, along with kuma menu and the icon theme built for it.

Mod+D opens the shell's launcher, which lists your applications and kuma's verbs together, Mod+Ctrl+V opens clipboard history and Mod+Ctrl+W the wallpaper picker; Mod+Shift+/ lists every bind. Wifi and bluetooth are in the control centre rather than in a GTK window from another desktop, and its header holds lock, log out, suspend, reboot and shut down.

Kuma configures it from the image: its own bar layout and fonts, its wallpaper, no first-login welcome screen, and two things noctalia ships disabled that would have been regressions to inherit, locking on idle and night light.

  • kuma menu is gone. Everything it offered that was kuma's is in your launcher as a desktop entry, on COSMIC as well as niri, which the menu never reached. Everything it offered that was a device setting belongs to the shell's control centre. kuma clean removes the launch-count cache it left in your home.

  • kuma edit opens the declaration this machine is actually using, in $EDITOR and otherwise nano, vim or vi. kuma edit --print prints the path it resolved without opening anything, which is the answer to "which kuma.toml am I editing" when a ./kuma.toml in the current directory is outranking ~/.config/kuma/kuma.toml.

Changed

  • The desktop follows one palette. On the niri desktop, kitty and GTK3 applications now take their colours from the palette noctalia is showing, on every change and again at login. That palette comes from the wallpaper by default, so changing the wallpaper changes the terminal, thunar, pavucontrol and nm-connection-editor with it; switch the shell to a built-in palette and they follow that instead. The image ships adw-gtk3-theme and GTK3 applications now use it rather than Adwaita.

This includes the terminal's sixteen ANSI colours. A palette generated from a wallpaper maps all of them into one hue family, so a diff's + and - come out as tints of the same colour; a palette picked by name keeps real hues. The generated colours arrive as ~/.config/kitty/themes/noctalia.conf and ~/.config/gtk-3.0/noctalia.css: delete them and their include lines to keep the image's fixed palette.

Fixed

  • A VM disk logs you into the shell its image declares. kuma vm gave its convenience account a bash login whatever [system].shell said, so a declaration reading shell = "fish" produced a VM that handed back bash. kuma install already honored it. Rebuild the disk to pick it up.

  • niri's Important Hotkeys overlay says what the keys do. The binds kuma splices into the session carried no titles, so the overlay that opens on first login named them by their command lines, one of which was an entire sh -c pipeline. The media keys are hidden from it now and the rest are named. Super+Alt+S is gone with them: it toggled a screen reader this image has never shipped, and a key that does nothing is worse than no key at all when the thing it claims to start is a screen reader.

Known limits

  • Kuma cannot see the settings you change from the desktop. The shell writes them to ~/.local/state/noctalia/settings.toml, which wins over the config kuma bakes into the image and which the image will never overwrite. Nothing in kuma reads that file, so kuma diff will say a machine matches its declaration while the desktop is visibly running something else. noctalia config export merged is what shows which settings are in effect.

  • GTK4 applications do not follow the palette, which on a kuma machine mostly means flatpaks. libadwaita ignores a user stylesheet that redefines its palette, so they keep their own dark theme while the terminal and every GTK3 application move.

Static x86_64 binary, no runtime dependencies.

$ curl -LO https://github.com/Letdown2491/kuma-linux/releases/download/v0.16.0/kuma-x86_64-unknown-linux-musl
$ chmod +x kuma-x86_64-unknown-linux-musl && sudo mv kuma-x86_64-unknown-linux-musl /usr/local/bin/kuma

Verify it came from this workflow:

$ cosign verify-blob \
    --bundle kuma-x86_64-unknown-linux-musl.bundle \
    --certificate-identity-regexp '^https://github.com/Letdown2491/kuma-linux/' \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    kuma-x86_64-unknown-linux-musl

Built from 78388d11a1543423a0cc223479f0b311571e3d23.

Assets 8
Loading