That was my first suspicion too. Thanks for the info.
It looks like this is the same issue, same error message in the journal: