fix: listener daemon read config from wrong HOME
enable_service baked Environment=HOME=$HOME into the unit at enable time; a stale/wrong shell HOME made the daemon read an empty ~/.config/linux_post_install/telegram_commands.env — commands showed in the bot menu (synced from the editor's correct HOME) but replying said "unknown command" and /help said none mapped. systemd user services already set the correct HOME; stop pinning it.
This commit is contained in:
@@ -366,7 +366,9 @@ Type=simple
|
||||
ExecStart=$runner --run
|
||||
Restart=always
|
||||
RestartSec=5
|
||||
Environment=HOME=$HOME
|
||||
# Do NOT pin Environment=HOME here — the systemd user manager already sets the
|
||||
# correct HOME for the user; pinning a stale enable-time value made the daemon
|
||||
# read ~/.config/... from the wrong home (menu shows commands, daemon says unknown).
|
||||
|
||||
[Install]
|
||||
WantedBy=default.target
|
||||
|
||||
Reference in New Issue
Block a user