^{Internally known as eu.kosy.Kerberos}

⚠️ Warning: This software is still in a development statues. Use on productive systems is not recommended. There might be major safety and stability problems. Multi monitors systems aren't supported at all.

Kerberos is a simple GTK 4 based lock screen for Wayland compositors. It is tested on Wayfire but should work on similar system as well (check dependencies).

It provides a simple screen shield with a login prompt and allows a custom background image and a few other settings. There is also a possibility to use you on CSS themes for your personal experience.

At the moment there are no available packages for Kerberos. If you want to install it check the instructions for an installation from the source code.

Build dependencies

• build essentials
• GTK 4 (>= 4.0)
• wayland-client (>= 1.19)
• libpam

Additional runtime dependencies

• wayland compositor
  • [Protocolls required by GTK]
  • wlr-input-inhibitor-unstable-v1
  • idle-inhibit-unstable-v1
• dbus
• swayidle (or simular)

# Clone project
git clone https://github.com/KosyTeam/kerberos.git
cd kerberos
# Build and (if desired) generate locales
make
make update-locale
# Install (requires root)
sudo make install

Kerberos does not provide a graphical interface to change its settings, but this can easily done with gsettings (alternatively dconf-editor could be used). Before doing this please take sure that everything installed without any error.

If using gsettings all commands are in the same format: gsettings set eu.kosy.Kerberos [key] [value]. See table for the specific settings.

*Not setting custom-theme-path will cause the default system theme to be used. This can be very buggy.

It's recommended to start Kerberos with an idle management daemon like swayidle. The command should be executed at startup or login and could look like the following:

swayidle -w \
timeout 300 'kerberos' \
before-sleep 'kerberos'

Please note that because of limitations in GTK 4 in combination with the wlr-layer-shell-unstable-v1-protocol some implementations will prevent further idle actions (like automatic suspend) after the start of Kerberos. For more information see #1.

Of course it's also possible to start Kerberos directly with the kerberos command. It's no problem to call Kerberos multiple times. If there is a running instance nothing will happen.

If the Mako notification daemon is reachable via dbus Kerberos will automatically show the number of missed notifications on the bottom of the screen. Other services are not yet supported.

The simplest way to get help is the Kosy Team Matrix Group alternativly you can also write a e-mail. There will be a solution on the way. If you have found a bug or a feature request than you can use our bug tracker, but please do not ask questions there.

I (mfxbe) use Kosy as a project name for number of applications I've written for personal use with a specific design and structure in mind. Right now Kerberos is the only one being available in public. Other might or might not be released in future.