crouton is broken for extended updates, Version 126.0.6478.252 (Official Build) (64-bit)

[CroutonIsFun]

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

cp: cannot create directory '/var/run/crouton/usr/local/chroots/focal/run/drm'
:permission denied

Please describe your issue:

crouton is broken for this build. This is unlike any previous errors. The chroot was working prior to the update.

@dnschneid @drinkcat @DennisLfromGA is there any fix for this?

If known, describe the steps to reproduce the issue:

All I can say is, update to the most recent release. However, I'm not on a "normal" channel:

Currently on long-term support candidate channel

I can revert to Stable, but this has disastrous consequences for my computing environment, like I can no longer watch TubiTV without DRM errors.

The 3 channels available are Stable, Beta, and Developer. If I leave the "long-term support candidate" channel, I cannot return to it without performing a powerwash and setting up extended support once again.

[CroutonIsFun]

I tried the following but it didn't fix the problem:

sudo mount -o remount,rw /var/run

I executed this prior to attempting to enter the chroot

Then I tried this:

sudo chmod -R 755 /var/run/crouton

but this didn't work either. If fact, the permissions of /var/run/crouton didn't change at all. ChromeOS must have this locked down...

[DennisLfromGA]

@CroutonIsFun,

The 3 channels available are Stable, Beta, and Developer.

In dev mode there is also a canary channel available but I don't think that will help with this issue.

If I leave the "long-term support candidate" channel, I cannot return to it without performing a powerwash and setting up extended support once again.

Also, in dev mode you can rollback to the previously installed version without a powerwash.
You can do it a couple of different ways, one with the crosh 'rollback' command:

--rollback (Perform a rollback to the previous partition.
The device will be powerwashed unless --nopowerwash is specified.) type: bool default: false

And with the 'cgpt' command:

cgpt add /dev/[disk] -i [inactive kernel partition] -S0 -T3
cgpt prioritize /dev/[disk] -i [inactive kernel partition]

I tend to use the 'cgpt' command, I have a script that does it.

But getting back to your original question, I no longer use crouton so I do not know if there is a fix for this.

-DennisLfromGA

[CroutonIsFun]

@CroutonIsFun,

The 3 channels available are Stable, Beta, and Developer.

In dev mode there is also a canary channel available but I don't think that will help with this issue.

If I leave the "long-term support candidate" channel, I cannot return to it without performing a powerwash and setting up extended support once again.

Also, in dev mode you can rollback to the previously installed version without a powerwash. You can do it a couple of different ways, one with the crosh 'rollback' command:

--rollback (Perform a rollback to the previous partition.
The device will be powerwashed unless --nopowerwash is specified.) type: bool default: false

And with the 'cgpt' command:

cgpt add /dev/[disk] -i [inactive kernel partition] -S0 -T3
cgpt prioritize /dev/[disk] -i [inactive kernel partition]

I tend to use the 'cgpt' command, I have a script that does it.

But getting back to your original question, I no longer use crouton so I do not know if there is a fix for this.

-DennisLfromGA

Thanks, sir, for taking a look. Yeah, I can rollback. I think I'll just stay on this channel. I have a nice dual boot to a thumb drive running Debian bookworm. And when I don't need direct device access, I can use crostini. Cheers!

[dnschneid]

If you're using xiwi you might be able to get away with disabling the dri stuff around here: https://github.com/dnschneid/crouton/blob/master/host-bin/enter-chroot#L568

That having been said, unless someone (@drinkcat ? :D ) digs through the Chromium git history or dev lists to determine what changed, it's going to be hard to come up with a practical solution.

[CroutonIsFun]

If you're using xiwi you might be able to get away with disabling the dri stuff around here: https://github.com/dnschneid/crouton/blob/master/host-bin/enter-chroot#L568

That having been said, unless someone (@drinkcat ? :D ) digs through the Chromium git history or dev lists to determine what changed, it's going to be hard to come up with a practical solution.

Hey, it's been a while since I checked the issues tab. I'm on a new Chromebook now. It uses an ARM processor. It's an ASUS Chromebook CM14 (CM1402C). I'm at Version 130.0.6723.126 (Official Build) (64-bit), and the Downloads folder is not accessible from the shell. You can only see it in the File Manager.

This means you can no longer make crouton executable. I feel very disoriented. This is not the Chromebook I had gotten used to.

There no longer seems to be a compelling reason to switch to developer mode.

[DennisLfromGA]

@CroutonIsFun,

I believe in a recent version they have removed Downloads from the home folder (~/Downloads), it is now only reachable from the MyFiles folder (~/MyFiles/Downloads). I have an alias for it now to make it easier to navigate to:

chronos@banshee-rev3 ~ $ ll ~/Downloads
ls: cannot access '/home/chronos/user/Downloads': No such file or directory
chronos@banshee-rev3 ~ $ alf cD=
(standard input):alias cD='cd ~/MyFiles/Downloads'

-DennisLfromGA

[CroutonIsFun]

@CroutonIsFun,

I believe in a recent version they have removed Downloads from the home folder (~/Downloads), it is now only reachable from the MyFiles folder (~/MyFiles/Downloads). I have an alias for it now to make it easier to navigate to:

chronos@banshee-rev3 ~ $ ll ~/Downloads
ls: cannot access '/home/chronos/user/Downloads': No such file or directory
chronos@banshee-rev3 ~ $ alf cD=
(standard input):alias cD='cd ~/MyFiles/Downloads'

-DennisLfromGA

Cool. I'll try again to see what happens.

[CroutonIsFun]

@dnschneid @DennisLfromGA @drinkcat

I just installed crouton on my Asus Chromebook CM1402C !!!

At this point, it's just a core and cli-extra install of focal, but I'm seeing no reason why I cannot install a full desktop.

Note: the integrated download directory does not get mounted, because its location has changed, but if I need to install a downloaded file, I can save it to my MicroSD card, which is available at /media/removable/foo.

Frankly, I'm confused now. Is it possible that crouton only works with ARM processors?

Update:

Drawbacks: besides the missing integrated Downloads directory, the keyboard target doesn't work. I was attempting to control audio settings with alsamixer, which requires using function keys as function keys. I used to be able to press Search + F5, for example to see all channels for a sound device, or Search + F6 to see all devices. Now this doesn't work, it just brings up a generic help text. Pressing only F5 or F6 activates the ChromeOS setting.

We really need to get cras back.

My Blue Snowball mic wasn't recognized properly: "this device has no adjustable settings".

This is a very advanced Chromebook. Crouton has fallen behind, and has not kept up with advances in technology. Meanwhile, Crostini is getting better, but it still lacks the ability to directly access devices.

Instead of trying to force fit the old crouton, we need a new version, and leave the old one alone.

This is all I have for now.