Buskill Failed to execute in Hyprland
Environment
OS: Kali linux rolling
Desktop Environment: Hyprland (Wayland)
Cable: Buskill cable cord
Description
BusKill works as expected on KDE Plasma. Disconnecting the BusKill cable successfully locks the screen.
However, when using Hyprland, disconnecting the cable results in a "failed to execute" error and the screen is not locked.
To Reproduce
Steps to reproduce the behavior:
- Boot into Hyprland.
- Start BusKill.
- Configure the lock-screen trigger.
- Disconnect the BusKill cable.
- Observe the error.
Screenshots

Log output: buskill.log
Additional context
Hyprland is a Wayland compositor rather than a traditional desktop environment like KDE Plasma or GNOME. Unlike those desktop environments, Hyprland requires users to configure many components themselves, including screen lockers. This may explain why BusKill's default lock command does not work.
For eg: I use hyprlock for screenlock
There are also other program used by hyprland user,
- hyprlock
- swaylock
- gtklock
Buskill Failed to execute in Hyprland
Environment
OS: Kali linux rolling
Desktop Environment: Hyprland (Wayland)
Cable: Buskill cable cord
Description
BusKill works as expected on KDE Plasma. Disconnecting the BusKill cable successfully locks the screen.
However, when using Hyprland, disconnecting the cable results in a "failed to execute" error and the screen is not locked.
To Reproduce
Steps to reproduce the behavior:
Screenshots

Log output: buskill.log
Additional context
Hyprland is a Wayland compositor rather than a traditional desktop environment like KDE Plasma or GNOME. Unlike those desktop environments, Hyprland requires users to configure many components themselves, including screen lockers. This may explain why BusKill's default lock command does not work.
For eg: I use hyprlock for screenlock
There are also other program used by hyprland user,