sdwdate is not supposed to be run in terminal under user user. Maybe useful during development without AppArmor profile. But otherwise sdwdate’s AppArmor profile doesn’t support that. And if it did, it might weaken AppArmor protections. Dunno. Maybe with some HOME variable in sdwdate apparmor profile it might work. I think running sdwdate under user user was discussed earlier in these forums somewhere. I am not sure what I should be doing in such situations. Changing the clock requires root or a capability. Therefore running under user user seems not useful. To simulate sdwdate from command line:
sudo systemctl stop sdwdate
sudo -u sdwdate sdwdate
That circumvents systemd sandboxing.
Otherwise sudo systemctl restart sdwdate so it’s run through its systemd unit with apparmor proifle and its systemd sandboxing.
Useful to see this when users post logs with sdwdate so I can answer what I just answered. But not considered an sdwdate bug.
This also happens without AAE. Minuscule bug affecting log output only.