Vasilis Koulis
Vasilis Koulis
Make sure that it is not installed with one of the following commands: ```bash systemctl --user status lnxlink.service sudo systemctl status lnxlink.service ``` If they don't work, then you can...
It seems that the pipx installation path is not on your PATH, so you will need to restart your terminal or computer or run lnxlink from that path: ```bash /home/dinth/.local/bin/lnxlink...
The systemd service is configured when you first launch lnxlink with the command I mentioned above: ```bash /home/dinth/.local/bin/lnxlink -sc config.yaml ```
You must have installed it as a user service. This means that you will have to run the systemctl command with the `--user` option. This is how to restart it:...
It seems that the -s option is not correct. You should run it without it and then the systemd service will be created. ```bash /home/dinth/.local/bin/lnxlink -c config.yaml ```
I've released the 2024.9.0 version of LNXlink. Please check if your issue is fixed.
Could you also provide the log files from the moment it starts? These are located at the same directory as your config file under the name `lnxlink.log`
The flatpak is very new addition, so I didn't have the time to write documentation for it. You will need to run it with the `-ic` option and the config...
That's great! I am currently trying to release a new version that runs without any arguments and sets the default path to `~/Documents/lnxlink.yaml`
That's a good idea. I am still figuring out how to make a flatpak release update, so I don't know when I'll have it done.