Short Summary
Information that could help -> systemd uses default KillMode=control-group ( i am not sure the behaviour of this ), documentation man 5 systemd.kill
Edit: found this https://stackoverflow.com/questions/40898077/systemd-systemctl-stop-aggressively-kills-subprocesses and https://man.archlinux.org/man/systemd.kill.5.en
Bitwarden is also electron app and it exits successfully ( exit code 0 ). Thats why i think there is bug in kando.
Steps to Reproduce the Issue
- use the above unit defination
- systemctl --user start kando.service
- systemctl --user stop kando.service
- systemctl --user status kando.service
exit=failure
Kando Version
v2.3.0
Installation Method
Via a package manger
Desktop Environment
Linux, Hyprland
Environment Version
ArchLinux
Additional Information
No response
Short Summary
Information that could help -> systemd uses default KillMode=control-group ( i am not sure the behaviour of this ), documentation
man 5 systemd.killEdit: found this https://stackoverflow.com/questions/40898077/systemd-systemctl-stop-aggressively-kills-subprocesses and https://man.archlinux.org/man/systemd.kill.5.en
Bitwarden is also electron app and it exits successfully ( exit code 0 ). Thats why i think there is bug in kando.
Steps to Reproduce the Issue
exit=failure
Kando Version
v2.3.0
Installation Method
Via a package manger
Desktop Environment
Linux, Hyprland
Environment Version
ArchLinux
Additional Information
No response