I am not sure whether this is a bug, but actually the NullLockBackend violates the contract that LockBackendInterface describes. This is all fine during install... until #1608842-165: Replace list of bootstrap modules, enabled modules, enabled themes, and default theme with config → came where we wanted to use lock to prevent an infinite loop and obviously it didn't work. This can be avoided by using a file based locking backend. It is still limited because it won't work as a real lock backend when multiple frontends are used however for install purposes we are still better off than null.
Postponed: needs info
9.5
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
If this is still a valid task could the issue summary be updated please?
There has been no work on this task for 12years. It is likely that it is no longer needed or has been implemented. Therefor, closing.
If there is work to do here, then either re-open the issue and add a comment or open a new issue and reference this one.