Help please.

[imarisimpson]

When I run the sudo install -Dt /usr/local/bin -m 755 ~/Downloads/crouton command it says Failed to complete chroot setup.Someone please help.

[DennisLfromGA]

That install command, if successful, has no output, it just installs crouton in your PATH so it's executable.

I believe you might be having trouble installing the chroot, that command would start with sudo crouton ...
Please show us the crouton command that's failing and we may be able to help with that.

Hope this helps,
-DennisLfromGA

[imarisimpson]

I don't understand sorry sir.

[imarisimpson]

Oooo I'm sorry you mean this?sudo crouton -t unity but I also tried xfce.

[imarisimpson]

Same thing happened.

[DennisLfromGA]

Please show us the entire crouton command that's failing and we may be able to help with that.

Hope this helps,
-DennisLfromGA

[imarisimpson]

Ok I am confused.Am I on the right track?

[DennisLfromGA]

I'm not sure, without any further details it's hard to tell.
Please show us a screenshot of what you are doing and what the errors are.

Hope this helps,
-DennisLfromGA

[imarisimpson]

Ok gotcha.

[imarisimpson]

[betapictoris]

Could you try a different release or target, I suggest sudo crouton -t xfce -r sid?
Make sure to run sudo edit-chroot -d xenial.

[imarisimpson]

No didn't work :/

[DennisLfromGA]

I tried both xenial & bionic with both unity & xfce and, after looking at the debbootstrap.log file, discovered that the root error is kernel revisions > 255, see below:

Selecting previously unselected package libc6:amd64.
    292 (Reading database ... 380 files and directories currently installed.)
    293 Preparing to unpack .../libc6_2.27-3ubuntu1_amd64.deb ...
    294 ERROR: Your kernel version indicates a revision number
    295 of 255 or greater.  Glibc has a number of built in
    296 assumptions that this revision number is less than 255.
    297 If you\'ve built your own kernel, please make sure that any
    298 custom version numbers are appended to the upstream
    299 kernel number with a dash or some other delimiter.

It was originally reported below but it affects more than just arm devices in my experience:

• crouton on arm, kernel version issue with libc updating in chroot · Issue crouton on x86_64 *and* arm, kernel version issue with libc updating in chroot #4429 · dnschneid/crouton
• sid installation issues on Chrome OS 90.0.4430.11 sid installation issues on Chrome OS 90.0.4430.11 #4434

The crouton devs are aware of this issue and are looking into it.

Hope this helps,
-DennisLfromGA

[imarisimpson]

Tysm hopefully they are able to fix it.

[imarisimpson]

So do you think this can be fixed or no?

[imarisimpson]

But it's crazy because I have downloaded this so many times before and never had that problem so it's random.

[viridianknight7]

Hi, i have the same problem, and i know you said that devs are looking into a solution, but will there actually be a solution? I just am concerned that this will be an abandoned issue. Hopefully, this post will be updated with a fix and I look forward to the soution.

[crowediddly]

I had the exact same issue, all available linux distros, multiple powerwashes, etc, on a 2015 Toshiba Chromebook 2. Turns out, the issue, at least on my end, was the distro channel I was on. All these errors occur on the chrome-os Developer's Channel. I finally went to the Stable channel, all issues went away, and install was simple as always.

[yoiammaac]

I am in stable though......

[jmjac]

Same issue on Chrome OS 90.0.4430.1 with kernel 4.4.257. Power washing and changing channels didn't help, but there is a temporary workaround (works for bionic and focal, xenial doesn't continue the installation after the interruption).

Crate a custom binary uname that on "uname -r" returns your kernel version x.y.z but with z lower than 255. In my case it was 4.4.254. Do sudo chmod +x /path/to/custome/uname to add execution permissions. Then during the installation process cancel it after "Moving bootstrap files into the chroot...". Backup the original uname with cd /usr/local/chroots/[chroot-name]/bin && sudo mv uname uname_originaland then copy the custom one with sudo cp /path/to/custom/uname /usr/local/chroots/[chroot-name]/bin. In another terminal do watch -n 0.2 sudo cp /path/to/custome/uname /usr/local/chroots/[chroot-name]/bin to repeat copy every 0.2s. Do sudo crouton -u -n [chroot-name] and continue. Later during the unpacking of coreutils your custom uname binary is going to be overwritten but the watch commad is going to take care of that. After you see "Configuring required packages..." the installation should continue without any problems and you can cancel the watch that was running in another terminal . This probably works because libc uses uname to lookup the kernel version.

After the successful installation you can replace the cusom uname with the backup of the original one with cd /usr/local/chroots/[chroot-name]/bin && sudo mv uname_original uname.

[siddhantsid]

Bro i dont have crostini support is there is any other way

This is the output of uname -a
Linux localhost 4.4.257-19935-g0ab0a71a40fd #1 SMP PREEMPT Mon Apr 19 20:04:52 PDT 2021 x86_64 Intel(R) Celeron(R) CPU N2840 @ 2.16GHz GenuineIntel GNU/Linux
chronos@localhost /mnt/stateful_partitio

[jmjac]

You could probably install chromebrew and use it to install go, but I have no experience with chromebrew at all. The uname that you want to create is really simple so you can do it in any language that creates a binary executable. It doesn't have to be go, I used it because it was the quickest to write for me.

[siddhantsid]

Thanks jmjackowiak
I successfully installed xenial

[yoiammaac]

can you give me tutorial or something with this method jmjac

[morphisjustfun]

You deserve a medal. BTW if you cant compile in another machine just use replit. It allows you to compile online and then you can download it.

[dinki]

Unfortunately I've ended up in the same place as some of these good folks. Can anyone tell me if a working solution has been found? I'm having the exact same problem as shown in the screenshots here:
#4441 (reply in thread)

Any help is most appreciated.

[siddhantsid]

@dinki you have not read the instructions by @jmjac nicely <
You have to replace it with your own again. It's a pretty short time window to do it, so I recommend quickly repeating sudo cp /path/to/custom/uname /usr/local/chroots/[chroot-name]/bin in another terminal window or setting up a script to do it for you. After you see "Configuring required packages..." >

[jmjac]

Yeah. When crouton is doing it's work after sudo crouton -u -n [chroot-name] you have another terminal open where you do watch -n 0.2 sudo cp /path/to/custome/uname . to repeat the copy command every 0.2s. If you get su: pam_start: error 26 you got the interruption timing wrong so delete-chroot and start again. It's a lot of trial and error to learn how to get it right consistently.

[jmjac]

Also do chmod +x on the custome uname before you copy it.

[dinki]

I thought I was coming back to claim victory using the tips you guys provided, but alas, no. It did get a lot farther but I ended up here:

Setting up libdrm-dev:amd64 (2.4.101-2~18.04.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
libdrm-dev set to automatically installed.
Compiling /usr/local/lib/croutonfreon.so...
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'xserver-xorg-video-all' is not installed, so not removed
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xorg : Depends: xserver-xorg (>= 1:7.7+19ubuntu7.1)
 xserver-xorg-video-intel : Depends: xorg-video-abi-23
                            Depends: xserver-xorg-core (>= 2:1.18.99.901)
E: Unable to correct problems, you have held broken packages.
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/bionic...
Sending SIGTERM to processes under /mnt/stateful_partition/crouton/chroots/bionic...

[jmjac]

@dinki That's a bionic problem. Try this https://github.com/dnschneid/crouton/wiki/3-Steps-to-Install-Bionic-Beaver