dnschneid / crouton

Chromium OS Universal Chroot Environment
https://goo.gl/fd3zc?si=1
BSD 3-Clause "New" or "Revised" License
8.57k stars 1.24k forks source link

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

Open CroutonIsFun opened 2 months ago

CroutonIsFun commented 2 months ago
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 commented 2 months ago

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 commented 2 months ago

@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 commented 1 month ago

@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 commented 1 month ago

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.