Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running via systemd does not work #103

Closed
FuzzyMistborn opened this issue May 5, 2024 · 1 comment
Closed

Running via systemd does not work #103

FuzzyMistborn opened this issue May 5, 2024 · 1 comment
Labels
bug Something isn't working no-issue-activity

Comments

@FuzzyMistborn
Copy link

FuzzyMistborn commented May 5, 2024

What type of installation are you running?

Desktop

Which Linux OS are you using?

Fedora 40

Which version of LNXLink has the issue?

2024.05

Describe the problem

I tried installing on Fedora 40. Everything works when I run the command in the terminal, but when I tried to run via systemd it kept failing/not running, showing a service 203/Exec error.

Additional context

Based on my searching for a solution, it seems SELinux doesn't like things outside "normal" paths. So /home/USER/.local/bin/lnxlink doesn't work. I changed the path/copied the binary over to /usr/local/bin, updated the systemd service file to the new path, and everything worked.

Is there a reason for the .local path? Could you install instead to /usr/local/bin?

Configuration

No response

Logs

May 04 22:25:07 test systemd[1]: lnxlink.service: Scheduled restart job, restart counter is at 76.
May 04 22:25:07 test systemd[1]: Started lnxlink.service - LNXlink.
May 04 22:25:07 test systemd[1]: lnxlink.service: Main process exited, code=exited, status=203/EXEC
May 04 22:25:07 test systemd[1]: lnxlink.service: Failed with result 'exit-code'.
@FuzzyMistborn FuzzyMistborn added the bug Something isn't working label May 5, 2024
Copy link

No activity on this issue recently. Make sure you update to the latest version of LNXlink to check if the issue has been resolved.
If no further activity occurs, the issue will be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working no-issue-activity
Projects
None yet
Development

No branches or pull requests

1 participant