ksergey / klipper-tg-bot Goto Github PK

add confirmation for restart, restart_firmware, etc

I had problems with the bot not automatically starting after my Raspberry Pi boots.
I ran sudo loginctl enable-linger ${USER}, as told by the README, but the bot still was not starting automatically.

After some research, this resolved my issue: StackExchange

It seems that the multi-user.target is not executed by user systemd, as was confirmed by running systemctl --user list-units --type=target:

  UNIT             LOAD   ACTIVE SUB    DESCRIPTION
  basic.target     loaded active active Basic System
  bluetooth.target loaded active active Bluetooth
  default.target   loaded active active Main User Target
  paths.target     loaded active active Paths
  sockets.target   loaded active active Sockets
  timers.target    loaded active active Timers

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
6 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

Workaround

I fixed the problem by following the solution in the provided StackExchange link.
I changed ~/.config/systemd/user/klipper-tg-bot.service's last line to WantedBy=default.target.
After the changes, I ran systemctl --user daemon-reload and systemctl --user enable klipper-tg-bot.service to finalize the changes.

Fix

To fix the problem altogether, you would only need to change this line to use default.target instead of multi-user.target:

I am using a Raspberry Pi 4 using Raspbian 11.