Part of my weekly "update/maintenance routine" on my desktop is syncing with eopkg every Friday/Saturday, rebooting, then checking the journal for errors. I keep a log of this too. I do this because it's a habit of mine coming from Arch a few months ago, it's probably not necessary anymore on Solus. The only time I was actually required to open the terminal out of necessity on Solus is to run the script to update ffmpeg-chromium on Vivaldi to fix the bird errors.
But these 3 errors, while not affecting anything from the end-user perspective, have prevailed since I first installed:
solus@user ~ $ sudo journalctl -p 3 -b
-- Journal begins at Sat 2021-11-20 16:22:18 CST, ends at Sat 2021-11-20 23:57:>
Nov 20 23:56:32 user systemd-tmpfiles[579]: Failed to copy files to /etc/issue>
Nov 20 23:56:34 user spice-vdagent[894]: Cannot access vdagent virtio channel >
Nov 20 23:56:34 user pulseaudio[1024]: [pulseaudio] pid.c: Daemon already runn>
Sorry the ends got cut off. Are these errors Solus-wide? Is there any way to get rid of them, or should I just not worry? On Arch, when an error popped up after an update, I'd research to solve it, but so far as it hasn't caused any real issues and I trust the process, I just leave it alone.