-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
crouton is broken for extended updates, Version 126.0.6478.252 (Official Build) (64-bit) #5097
Comments
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... |
In dev mode there is also a canary channel available but I don't think that will help with this issue.
Also, in dev mode you can rollback to the previously installed version without a powerwash.
And with the 'cgpt' command:
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! |
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. |
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.
The text was updated successfully, but these errors were encountered: