The problem seems to be that the command grub2-set-bootflag is being run as the logged in user, and within grub2-set-bootflag, a setuid(0) command fails (presume trying to set the user to 'root').
Given that ALL users signing in would result in the same bootflag being set (if the above worked) it seems unlikely the bootflag serves any real useful purpose anyway, so perhaps this 'service' should be stopped from running anyway. But at the moment it is not working and is resulting in regular errors reported in 'messages'.
Example error:
[Grub2 Error grub-boot-success.service: Main process exited, code=exited, status=1/FAILURE]
Reproduce error by logging in via SSH as any user, two minutes later 'systemd' attempts to run the command in:
/usr/lib/systemd/user/grub-boot-success.service
This by default tries to run:
[Service] Type=oneshot ExecStart=/usr/sbin/grub2-set-bootflag boot_success
Which fails with the above error.
The problem seems to be that the command grub2-set-bootflag is being run as the logged in user, and within grub2-set-bootflag, a setuid(0) command fails (presume trying to set the user to 'root').
Given that ALL users signing in would result in the same bootflag being set (if the above worked) it seems unlikely the bootflag serves any real useful purpose anyway, so perhaps this 'service' should be stopped from running anyway. But at the moment it is not working and is resulting in regular errors reported in 'messages'.