Trying to launch Crouton after installing ChromeBrew but failed about crouton HOT 4 CLOSED

I had the same issue after updating to chromeos 126 and was only able to regain access to my chroot by reverting to 125 and restoring the back up. As chromebrew worked normally with 126 it seems like there's an issue with crouton and this update.

What I tried:
enter-chroot caused system to restart as soon as I enter my encryption password
Following this forced restart commands returned a new prompt but no output
Powerwash was required to get commands to work again
Chromebrew installed normally as did crew-sudo
Crouton launcher could be installed as executable
Restoring chroot from back up successfully installed launcher and began copying files to stateful_partition but always caused system restart after entering encryption password
Creating a new chroot failed with system restart at downloading launcher

What worked
Reverting chromeos to 125

from crouton.

I had the same issue after updating to chromeos 126 and was only able to regain access to my chroot by reverting to 125 and restoring the back up. As chromebrew worked normally with 126 it seems like there's an issue with crouton and this update.

What I tried: enter-chroot caused system to restart as soon as I enter my encryption password Following this forced restart commands returned a new prompt but no output Powerwash was required to get commands to work again Chromebrew installed normally as did crew-sudo Crouton launcher could be installed as executable Restoring chroot from back up successfully installed launcher and began copying files to stateful_partition but always caused system restart after entering encryption password Creating a new chroot failed with system restart at downloading launcher

What worked Reverting chromeos to 125

I've tried to revert my Chromebook to 125 but failed... then I ran the Ctrl+Shift+Alt+R after Powerwash but the Revert button didn't appear

from crouton.

This was actually fixed a little while ago. If you're already on 126 restoring from back up or installing a new chroot should both work again. You need to download the launcher again and use the crouton command with the -f flag to restore a backup, not edit-chroot. That will ensure that the latest version of the installer, which corrects the incompatibility issue, is used. If you did manage to revert to 125 then running an update on your chroot should enable you to update to 126 without any further problems.

from crouton.

This was actually fixed a little while ago. If you're already on 126 restoring from back up or installing a new chroot should both work again. You need to download the launcher again and use the crouton command with the -f flag to restore a backup, not edit-chroot. That will ensure that the latest version of the installer, which corrects the incompatibility issue, is used. If you did manage to revert to 125 then running an update on your chroot should enable you to update to 126 without any further problems.

Thanks... I've tried to reinstall Crouton and now it works

from crouton.