Not sure what the issue is, but I am not that experienced either … did you do the reboot after an upgrade? In this thread, a similar error message was experienced, and a github issue was opened, referencing a workaround thread if it went wrong: