Result of ‘sudo edit-chroot -all’:
name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20221126232257~master:ae594340
release: xenial
architecture: amd64
targets: xfce
host: version 15373.0.0 (Official Build) dev-channel octopus
kernel: Linux localhost 4.14.254-20300-g04f9d4e19110 #1 SMP PREEMPT Sat Mar 4 20:21:26 PST 2023 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
I am very new to this stuff, so please be nice about it.
I keep having this issue and I cannot install a chroot:
sed: can't read common/cras_messages.h: No such file or directory
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
Hey guys, I am facing the same issue if I simply follow the readme. Was this issue resolved in any commit? Is it worth the hussle to try to build it from source? If anyone has tried yet, I’d appreciate the feedback 😃
@EPICTHUNDER123 Im using ChromeOs 114.0.5735.239. We both have dev mode enabled and are on the stable channel. Our versions are similar and aren’t the reason of such error.
Probably you didn’t install the crouton browser extension. install it from here I don’t know what it fully does but it has some debugging and logging features.
if it doesn’t work then type
sudo startxfce4again, again, and again. And it worked in my case. I don’t know the reason why it sometimes does that.If it then doesn’t work, then i I don’t know what it could be. I know that its not the type of chromebook bc their software are mostly standard.
I got past this by executing from /usr/local like this: sudo -cp ~/Downloads/crouton /usr/local, and then sudo sh /usr/local/crouton -kali-rolling.
What a coincidence. I’ve been using the same chromebook as you and you might have the same error as me!!
Can you tell me the ChromeOs version you are using and what channel it is on (i.e stable, beta, dev) so that we can relate? And what command you used to create the chroot (i.e sudo CROUTON_BRANCH=silence crouton <something>)?
Im curious if our identical chromebooks have the same issue or not depending on the version and commands.
_
_ So, its fairly straight forward actually. If you’ve already made a chroot that is currently incomplete, (and haven’t specified a name for it (-n) then inevitably it will be named after the distro you chose to install. So all you’d need to do now at this point would be to update your chroot using the “-u” variable. So lets say the distro you chose was xenial and you said you wanted the xfce desktop environment. So therefore your command would look like this:
sudo CROUTON_BRANCH=silence crouton -u -r xenial -t xfceOr lets say you deleted your chroot and you wanted to start a brand new one. You can do the same thing pretty much, only you’d drop the “-u” option since you won’t be updating an already existing chroot. So in this case your command would look like this:
sudo CROUTON_BRANCH=silence crouton -r xenial -t xfceSo remember, you can interchange xenial with the distro of your choosing. Whether that be Ubuntu’s focal, jammy, impish, kinetic, etc… Or whether you would like to use Debian’s buster, bullseye, bookworm, sid, etc… You can also add whatever other targets as well after the “-t” option, using a comma (no space) to separate each. Here’s a few examples:
sudo CROUTON_BRANCH=silence crouton -r xenial -t xfce,xfce-desktop,core,keyboard,xiwi,x11,cli-extra,extensionI have the same issue. I’m pretty sure some people have this issue.