Installing Kando on Linux

On Linux, you can either install Kando from your package manager, or via any of the pre-packaged binaries from GitHub releases.

Supported Desktop Environments

Implementing a menu like Kando for various desktop environments is not exactly easy. Things like getting the mouse position before opening a window, simulating key presses, or getting the name of the currently focused application window may have to be implemented differently.

Environment	Status	Notes
GNOME / X11	✅
GNOME / Wayland	✅	Requires adapter GNOME Shell extension which provides a DBus interface for Kando to communicate with.
KDE / X11	✅
KDE / Wayland	✅	Works both on Plasma 5 and Plasma 6. See below for how to bind global shortcuts.
Cosmic	❌	Contributions are welcome! Read the corresponding feature request.
Hyprland	✅	See below for the required configs.
Cinnamon	✅
XFCE	✅
MATE	✅
Budgie	✅
LXQt	✅
LXDE	✅	Requires a compositor for the transparency to work.
Openbox	✅	Requires a compositor for the transparency to work.
i3	✅	Requires a compositor for the transparency to work.
dusk	✅	Requires a compositor for the transparency to work. See below for the required config.
Qtile	➖	It works with some flaws. Contributions are welcome! Read the corresponding bug report.
Niri	❌	Contributions are welcome! Read the corresponding feature request.

Have you tested another environment?

If you have tested Kando on another desktop environment, please add it to the list above by editing this page on GitHub!

Installation via a Package Manager

1. Kando is already available in several package managers.

   Flathub

   Kando is available on Flathub.

   flatpak install flathub menu.kando.Kando

   AUR

   You can install kando-bin from the AUR.

   yay -S kando-bin

   NixOS

   A kando package is available in Nixpkgs.

   nix-shell -p kando

   AM or AppMan

   You can install Kando from the AppMan package manager.

   am -i kando

2. After the installation, you can start Kando from your application launcher! Not much will happen, as Kando is a tray application and will run in the background.

3. On most X11 based distributions, you can now press Ctrl + Space to open the example menu!

   This does not work?

   On some desktop environments, especially those based on Wayland, you will have to perform some additional steps. Read more in the Desktop Specifics section below for more information.

Installation via a Pre-Packaged Binary

1. Just head over to the releases page and download a package that fits your distribution.

   Ubuntu

   On Ubuntu and other Debian-based distributions, you can download the Kando_*_amd64.deb package.

   Fedora

   On Fedora and other RPM-based distributions, you can download the Kando-*.x86_64.rpm package.

   AppImage

   The Kando-*-x86_64.AppImage package is a universal package that should work on most distributions.

   Zip Archive

   The Kando-linux-x64-*.zip package is a generic package that should work on most distributions.

2. Install the package. The AppImage and Zip Archive packages are standalone and can be run directly. The other packages need to be installed.

   Ubuntu

   sudo dpkg -i Kando_*_amd64.deb

   After the installation, you can start Kando from your application launcher! Not much will happen, as Kando is a tray application and will run in the background.

   Fedora

   sudo rpm -i Kando-*.x86_64.rpm

   After the installation, you can start Kando from your application launcher! Not much will happen, as Kando is a tray application and will run in the background.

   AppImage

   chmod +x Kando-*-x86_64.AppImage
   ./Kando-*-x86_64.AppImage

   Zip Archive

   unzip Kando-linux-x64-*.zip
   ./Kando-linux-x64/kando

3. On most X11 based distributions, you can now press Ctrl + Space to open the example menu!

   This does not work?

   On some desktop environments, especially those based on Wayland, you will have to perform some additional steps. Read more in the Desktop Specifics section below for more information.

Desktop Specifics

Implementing a menu like Kando on Wayland is not exactly easy. Things like getting the mouse position before opening a window, simulating key presses, or getting the name of the currently focused application window does not work out of the box. Therefore, Kando needs some additional setup on Wayland based desktop environments. There are also some X11 based desktop environments that need some additional setup.

GNOME on Wayland

You will also need to install the 🐚 Kando Integration Extension. Via a D-Bus interface, it provides the name of the currently focused window, and the current mouse pointer position. Furthermore, it allows registering and simulating keyboard shortcuts.

KDE Plasma on Wayland

If you are using Plasma on Wayland, Kando cannot directly bind global shortcuts. Instead, it uses the Global-Shortcuts Desktop Portal. This means, you specify a shortcut ID for each menu in Kando’s menu editor. Once you inserted an ID, the KDE’s system settings will pop up automatically and you can assign a shortcut to the ID.

It is perfectly fine to use the same shortcut ID for multiple menus. Use this in combination with the app-dependent menu feature to open different menus depending on the currently focused application!

Hyprland

You will need some window rules for Kando. Else, the menu will not float above other windows.

~/.config/hypr/hyprland.conf

windowrule = noblur, class:kando
windowrule = opaque, class:kando
windowrule = size 100% 100%, class:kando
windowrule = noborder, class:kando
windowrule = noanim, class:kando
windowrule = float, class:kando
windowrule = pin, class:kando

Also, Kando cannot directly bind global shortcuts on Hyprland. Instead, you specify a shortcut ID for each menu in Kando’s menu editor and bind a key combination in hyprland.conf. To get the exact shortcut ID, you can use hyperctl globalshortcuts to list all currently registered global shortcuts. If you run the flatpak version of Kando and chose example-menu as the shortcut ID, you can would bind it like this:

~/.config/hypr/hyprland.conf

bind = CTRL, Space, global, menu.kando.Kando:example-menu

Furthermore

1. Toggling Special-Workspace through kando-menu will be glitchy (i.e in some cases special-workspace will reopen instead of closing). See https://github.com/kando-menu/kando/issues/784

2. After triggering kando-menu-item of type Run command whose target is activewindow will not work correctly as by default Hyprland restores focus_on_close to next candidate window. See https://github.com/kando-menu/kando/issues/812

   Both of above can be solved by using the following config

   ~/.config/hypr/hyprland.conf

   input {
       special_fallthrough = true # having only floating windows in the special workspace will not block focusing windows in the regular workspace.
       focus_on_close = 1 # focus will shift to the window under the cursor.
   }

3. Using the solution for 2nd step might not work in situations where the target window is small as you will travel out of target area while activating items from sub-menu. For that you can use hyprctl dispatcher focusurgentorlast or hyprctl dispatcher focuscurrentorlast instead. See https://wiki.hyprland.org/Configuring/Dispatchers/#list-of-dispatchers

Dusk

On Dusk, you will have to install and use a compositor like picom or compton to make the transparency work. Also, you will need some window rules for Kando:

dusk/config.def.h

static const Rule clientrules[] = {
  { .class = "kando", .flags = FullScreen }, //kando should be on top of DOCK clientrule
  { .wintype = WTYPE "DESKTOP", .flags = Unmanaged|Lower },
  { .wintype = WTYPE "DOCK", .flags = Unmanaged|Raise },
};

LXDE, i3, Openbox, and others

On some minimal desktop environments, you will have to install and use a compositor like picom or compton to make the transparency work.