Comment 1 for bug 1861525

Wondered in here randomly, but .. it is normal for there to be a per-user systemd process on interactive systems - it manages jobs for that user when logged in. If there is no user logged in, it may still exist if 'loginctl enable-linger' has been called for that user - it allows the per-user systemd to start and monitor background services for the user (things that in the old days we might have started from cron, or using nohup.)

The permission denied error message normally occurs when one or more of the path components /home/ubuntu/.config/systemd/user have ended up not owned by the user.