Dispatcher seems to lose track of who the username is... not sure if this is a regression or something new.
Feb 10 09:16:58 uruk NetworkManager[496]: <info> NetworkManager state is now CONNECTED_GLOBAL
Feb 10 09:16:58 uruk NetworkManager[496]: <info> Policy set 'Marriott_GUEST' (wlp3s0) as default for IPv4 routing and DNS.
Feb 10 09:16:58 uruk NetworkManager[496]: <info> Writing DNS information to /usr/bin/resolvconf
Feb 10 09:16:58 uruk NetworkManager[496]: <info> (wlp3s0): Activation: successful, device activated.
Feb 10 09:16:58 uruk nm-dispatcher[497]: Dispatching action 'up' for wlp3s0
Feb 10 09:16:58 uruk nm-dispatcher[497]: Chrony going online.
Feb 10 09:16:58 uruk nm-dispatcher[497]: 200 OK
Feb 10 09:16:58 uruk systemd[875]: Failed at step USER spawning /usr/bin/insync: No such process
Feb 10 09:16:58 uruk systemd[1]: insync@\x28unknown\x29.service: main process exited, code=exited, status=217/USER
Feb 10 09:16:58 uruk systemd[1]: Failed to start Insync.
Feb 10 09:16:58 uruk systemd[1]: Unit insync@\x28unknown\x29.service entered failed state.
Feb 10 09:16:58 uruk systemd[1]: insync@\x28unknown\x29.service failed.
Feb 10 09:16:58 uruk nm-dispatcher[497]: Job for insync@\x28unknown\x29.service failed. See "systemctl status 'insync@\x28unknown\x29.service'" and "journalct
Feb 10 09:16:58 uruk nm-dispatcher[497]: Script '/etc/NetworkManager/dispatcher.d/10-insync' exited with error status 1.
Feb 10 09:16:58 uruk NetworkManager[496]: <warn> (2) 10-insync failed (failed): Script '/etc/NetworkManager/dispatcher.d/10-insync' exited with error status
Feb 10 09:16:58 uruk NetworkManager[496]: <info> startup complete
Dispatcher seems to lose track of who the username is... not sure if this is a regression or something new.