Closed garcialn closed 4 months ago
Maybe simplify and instead of this:
--cfg $${HOME}/.config/kanata/config.kbd
try the absolute path instead:
--cfg /home/garcia-ln/.config/kanata/config.kbd
I did try but got the same response from systemctl --user status kanata.service
.
Oh I skimmed over the error too quickly.
Looks like the same problem as in this comment: https://github.com/jtroo/kanata/issues/1153#issuecomment-2265690809
kanata isn't found in $PATH
of the systemd env.
It was, indeed, the $PATH var that cause the problem. Just changed locations and it worked correctly. Thank you for the help and congrats for the amazing project!!
Requirements
Describe the bug
Problem
I installed kanata and running with
sudo ~/.cargo/bin/kanata -c ~/.config/kanata/config.kbd
it works fine, and withsh -c 'exec $(which kanata) --cfg $HOME/.config/kanata/config.kbd'
, it also works, but when trying to run withsystemctl --user start kanata.service
(so that it can run while booting), i get the 127 status code return (exit code).Setup
Relevant kanata config
.config/systemd/user/kanata.service
.config/kanata/config.kbd
To Reproduce
Expected behavior
Run
kanata.service
with no problems.Kanata version
kanata 1.6.1
Debug logs
I did go through the linux setup doc (including the
input
anduinput
to my user group, and adding the udev rule), but when getting to the final part, runningsystemctl --user status kanata.service
, this is the output:Operating system
Linux
Additional context
From the output of
systemctl --user status kanata.service', it shows problem with the
.config/kanata/config.kbd... I tried changing the config file location (and changing also the reference to it in
katana.service`), but nothing changed... I'm gonna keep trying something about it until debugging shows me it's something else... If someone has any idea of what the problem might be, i'd be thankful for the info... 😉