* check state.json
* delete state.json
* restart and do a new snap install of core
### Check state.json
`sudo ls -lah /var/lib/snapd/state.json`
output should be something like
`-rw------- 1 root root 38K Jun 11 11:56 /var/lib/snapd/state.json`
### Delete state.json
You can mv-rename the old file if you wish. I simply
`sudo rm /var/lib/snapd/state.json`
### Restart Container
you can exit and reboot chromeos or
sudo reboot,
or if you access via lx, log out into lxc and stop/start the container and login
## Issue
To the extent this helps anyone rediscovering this problem...
env penguin container in the chrome os termina VM:
running Debian11 zsh shell
`cannot setup udev for snap "core": cannot run udev triggers: exit status 1`
running through various snap debugs, there was also a state json error
`snap error: cannot read the state file: open state.json: no such file or directory`
## Solution
**Note - will delete information about previous snap installs.**
from [snapcraft forum](https:/ /forum. snapcraft. io/t/snapd- cannot- run-daemon- cannot- read-state- unexpected- eof/17908/ 2)
* check state.json
* delete state.json
* restart and do a new snap install of core
### Check state.json snapd/state. json` snapd/state. json`
`sudo ls -lah /var/lib/
output should be something like
`-rw------- 1 root root 38K Jun 11 11:56 /var/lib/
### Delete state.json snapd/state. json`
You can mv-rename the old file if you wish. I simply
`sudo rm /var/lib/
### Restart Container
you can exit and reboot chromeos or
sudo reboot,
or if you access via lx, log out into lxc and stop/start the container and login
Then simply run
`sudo snap install core`
Worked for me - good luck