Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to launch Crouton after installing ChromeBrew but failed #5086

Closed
anak-negeri opened this issue Jul 3, 2024 · 4 comments
Closed

Trying to launch Crouton after installing ChromeBrew but failed #5086

anak-negeri opened this issue Jul 3, 2024 · 4 comments

Comments

@anak-negeri
Copy link

Please paste the output of the following command here: sudo edit-chroot -all

![20240703_140555](https://github.com/dnschneid/crouton/assets/174587353/78dd4658-4214-443b-a0a3-95876e435573)

Please describe your issue:

I've followed the guide to install Crouton using ChromeBrew (https://github.com/dnschneid/crouton/wiki/(CIF000)-Fixing-Crouton-Using-Chromebrew)

But when I tried to "startxfce4" nothing happened
Screenshot 2024-07-03 14 03 58

And here is the .bashrc file
Screenshot 2024-07-03 14 04 32

Is there any way to fix it???

Note: I tried to use ChromeBrew because the previous method using enter-chroot after "mount -o remount,rw /sys/kernel/security" made my Chromebook restarted itself since this morning

@Equus-paradoxus
Copy link

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

@anak-negeri
Copy link
Author

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

@Equus-paradoxus
Copy link

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.

@anak-negeri
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants