[GH-ISSUE #265] MacOS launchd failed to run #134

New issue

Open

opened 2026-05-05 22:10:56 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 22:10:56 -06:00

Owner

Originally created by @robotJie on GitHub (Feb 16, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/265

OS: MacOS

Everything works as expected when I run lan-mouse directly in a shell/terminal.

However, I want lan-mouse to start automatically at system boot. So, I created a .plist file in /Library/LaunchDaemons and loaded/enabled it. Unfortunately, the program is failing to run as a LaunchDaemon.

The error log is shown below (I've already set LAN_MOUSE_DEBUG_LEVEL=debug in the .plist file,but nothing different):

I initially suspected a config environment issue. But even after explicitly specifying the config file path, the problem remains.

Any ideas on what might be causing this?

Originally created by @robotJie on GitHub (Feb 16, 2025). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/265 OS: MacOS Everything works as expected when I run lan-mouse directly in a shell/terminal. However, I want lan-mouse to start automatically at system boot. So, I created a .plist file in /Library/LaunchDaemons and loaded/enabled it. Unfortunately, the program is failing to run as a LaunchDaemon. The error log is shown below (I've already set LAN_MOUSE_DEBUG_LEVEL=debug in the .plist file,but nothing different): ![Image](https://github.com/user-attachments/assets/27cacad0-0073-4f8e-aa13-3f91d5d09c23) I initially suspected a config environment issue. But even after explicitly specifying the config file path, the problem remains. Any ideas on what might be causing this?

gitea-mirror commented

2026-05-05 22:10:58 -06:00

Author

Owner

@feschber commented on GitHub (Feb 16, 2025):

Looks like the $HOME environment variable is not set, so it does not know where to look for the config file.
Can you try settings that variable? (you seem to know how to do that)

@feschber commented on GitHub (Feb 16, 2025): Looks like the `$HOME` environment variable is not set, so it does not know where to look for the config file. Can you try settings that variable? (you seem to know how to do that)

gitea-mirror commented

2026-05-05 22:10:58 -06:00

Author

Owner

@feschber commented on GitHub (Feb 16, 2025):

alternatively you shoud be able to set $XDG_CONFIG_HOME to your ~/.config/ directory

@feschber commented on GitHub (Feb 16, 2025): alternatively you shoud be able to set `$XDG_CONFIG_HOME` to your `~/.config/` directory

gitea-mirror commented

2026-05-05 22:11:00 -06:00

Author

Owner

@robotJie commented on GitHub (Feb 17, 2025):

I tried explicitly specifying the config file path using the -c option. Additionally, I attempted setting environment variables, but neither of these methods resolved the issue

The .plist file is shown below:

@robotJie commented on GitHub (Feb 17, 2025): I tried explicitly specifying the config file path using the -c option. Additionally, I attempted setting environment variables, but neither of these methods resolved the issue The .plist file is shown below: ![Image](https://github.com/user-attachments/assets/1ef38e47-0f4d-4178-b1fb-ba6cf0da7ad7)

gitea-mirror commented

2026-05-05 22:11:01 -06:00

Author

Owner

@feschber commented on GitHub (Feb 18, 2025):

Could paste the full log here?

@feschber commented on GitHub (Feb 18, 2025): Could paste the full log here?