Yes, as I stated in the post it did not seem to affect the working of my system in nay way.
This morning boot, after last night update, had no such error.
So we will put it to a temporary aberration!
I have a few errors in the boot but none that causes any malfunction of the system in my usual working day.
Here were the errors this AM:
Feb 06 05:36:46 kaisen systemd-udevd[497]: event_source: Failed to get device name: No such file or directory
Feb 06 05:36:48 kaisen nvidia-persistenced[883]: Failed to open libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object file: No such file or directory
Feb 06 05:36:48 kaisen systemd[1]: Failed to start nvidia-persistenced.service - NVIDIA Persistence Daemon.
Feb 06 05:36:52 kaisen pulseaudio[1260]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
Feb 06 05:37:30 kaisen lightdm[2138]: gkr-pam: unable to locate daemon control file
Feb 06 05:37:30 kaisen pulseaudio[1260]: Error opening PCM device hdmi:1,1: Permission denied
Feb 06 05:37:30 kaisen pulseaudio[1260]: Error opening PCM device front:0: No such file or directory Feb 06 05:37:30 kaisen pulseaudio[1260]: Error opening PCM device front:0: No such file or directory Feb 06 05:37:31 kaisen pulseaudio[2176]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
Feb 06 05:37:33 kaisen systemd[2160]: Failed to start app-kaisen\x2dgtk[x2dsettings@autostart.service](mailto:x2dsettings@autostart.service) - Kaisen GTK settings.
Feb 06 05:37:35 kaisen xdg-desktop-portal[3091]: pw.conf: can’t load default config client.conf: No such file or directory
The pulse audio is a timing issue I think. It doesn’t come on in time. Thhe bluez is because I have bluetooth service disabled by default. The others, I am not sure, but they don’t seem to create any issues.