As discussed on call, removing the pgadmin4.db file made it work.
Unfortunately, the exact reason for error could not be found.
Corrupted layout state? Maybe we can detect that and forcefully reset it.
Yes looks like. Need to check how we can detect it.
At least if we get another case we should see if it's possible to fix it by deleting only the layout state from the database, rather than the entire database (if feasible)
