Closed duffydack closed 11 months ago
systemctl --user start a2ln gives failure to start with this in logs.
systemctl --user start a2ln
× a2ln.service - Android 2 Linux Notifications Server Loaded: loaded (/usr/lib/systemd/user/a2ln.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sat 2023-11-04 14:08:45 GMT; 1s ago Duration: 136ms Process: 4091 ExecStart=/usr/bin/a2ln --no-pairing-server (code=exited, status=2) Main PID: 4091 (code=exited, status=2) CPU: 135ms Nov 04 14:08:44 spock systemd[1228]: Started Android 2 Linux Notifications Server. Nov 04 14:08:45 spock a2ln[4091]: usage: a2ln [-h] [--ip IP] [--port PORT] [--title-format TITLE_FORMAT] Nov 04 14:08:45 spock a2ln[4091]: [--body-format BODY_FORMAT] [--command COMMAND] Nov 04 14:08:45 spock a2ln[4091]: {version,pairing} ... Nov 04 14:08:45 spock a2ln[4091]: a2ln: error: unrecognized arguments: --no-pairing-server Nov 04 14:08:45 spock systemd[1228]: a2ln.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Nov 04 14:08:45 spock systemd[1228]: a2ln.service: Failed with result 'exit-code'.
Starting from shell with just a2ln, or editing service file and removing --no-pairing-server it works as intended.
a2ln
--no-pairing-server
Fixed with 1.1.14.
Description
systemctl --user start a2ln
gives failure to start with this in logs.Starting from shell with just
a2ln
, or editing service file and removing--no-pairing-server
it works as intended.