crouton
crouton copied to clipboard
Debootstrap; Permission Denied
chronos@localhost / $ sudo crouton -t xfce
Every time I type the command I get this:
WARNING: Your rootfs is writable. Signed boot verification cannot be enabled. If this is a surprise to you, you should do a full system recovery via USB. Installing xenial-amd64 chroot to /usr/local/chroots/xenial Downloading bootstrap files... /tmp/crouton-installer-cache/crouton: 95: /tmp/crouton-installer-cache/crouton.3x9/installer/ubuntu/bootstrap: /tmp/crouton.UZp/debootstrap: Permission denied debootstrap error log: tail: cannot open '/tmp/crouton.UZp/xenial-amd64/debootstrap/debootstrap.log' for reading: No such file or directory Failed to run debootstrap.
If known, describe the steps to reproduce the issue:
Have the same issue. Appears Crouton is out of date
Try
sudo crouton -r focal -t xfce
chronos@localhost / $ sudo crouton -t xfce
Every time I type the command I get this:
WARNING: Your rootfs is writable. Signed boot verification cannot be enabled. If this is a surprise to you, you should do a full system recovery via USB. Installing xenial-amd64 chroot to /usr/local/chroots/xenial Downloading bootstrap files... /tmp/crouton-installer-cache/crouton: 95: /tmp/crouton-installer-cache/crouton.3x9/installer/ubuntu/bootstrap: /tmp/crouton.UZp/debootstrap: Permission denied debootstrap error log: tail: cannot open '/tmp/crouton.UZp/xenial-amd64/debootstrap/debootstrap.log' for reading: No such file or directory Failed to run debootstrap.
If known, describe the steps to reproduce the issue:
Hey, i can't reproduce this error:
chronos@localhost / $ sudo /usr/local/bin/crouton -t xfce
WARNING: USB booting is enabled; consider disabling it.
WARNING: Signed boot verification is disabled; consider enabling it.
You can use the following command: sudo crossystem dev_boot_usb=0 dev_boot_signed_only=1
Installing xenial-amd64 chroot to /usr/local/chroots/xenial
Downloading bootstrap files...
W: Cannot check Release signature; keyring file not available /usr/share/keyrings/ubuntu-archive-keyring.gpg
I: Retrieving InRelease
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on http://archive.ubuntu.com/ubuntu...
I: Retrieving adduser 3.113+nmu3ubuntu4
I: Validating adduser 3.113+nmu3ubuntu4
I: Retrieving apt 1.2.10ubuntu1
Please try an sudo mount -i -o remount,exec /tmp/
, after this try crouton install again.
having the same problem i think chrome updated something that stopped this from working. im currently trying to get crouton for the first time and im stuck at this step
having the same problem i think chrome updated something that stopped this from working. im currently trying to get crouton for the first time and im stuck at this step
Have you tried my instructions? Then, i still can't reproduce the error.
having the same problem i think chrome updated something that stopped this from working. im currently trying to get crouton for the first time and im stuck at this step
Have you tried my instructions? Then, i still can't reproduce the error.
I have but its still the same error
Can be fixed via powerwash of Chromebook. See -> https://github.com/dnschneid/crouton/issues/4805
Please close issue @avaiv
its still getting the same error even after i tried powerwashing and after i tried all of your suggestions. maybe try looking into how to getting by the permission denied bit?
The problem is, that i can't reproduce the error, also there is no logic behind this error, because of following things:
- You run script as sudo
- on line 95 in
installer/crouton
is nothing (empty line) - on line 95 in
direct crouton binary
is nothing, only an check of verbose options.
If you are not using and self editited or some other modificated version of crouton, than its hard to say where the problem is here.
The permission error comes from your system and not crouton, so the problem is not on crouton side here. @avaiv Can you please give us the output of sudo ls -la /tmp/
(in second tab, also after typing shell) shortly after starting install.
The problem is, that i can't reproduce the error, also there is no logic behind this error, because of following things:
- You run script as sudo
- on line 95 in
installer/crouton
is nothing (empty line) - on line 95 in
direct crouton binary
is nothing, only an check of verbose options.
If you are not using and self editited or some other modificated version of crouton, than its hard to say where the problem is here.
Okay, i have done some forensics... and found where the error comes. Need future inspecting to understand the code lines and see if i could found the issue.
Line 95 from installer/ubuntu/bootstrap
# Grab the release and drop it into the subdirectory
echo 'Downloading bootstrap files...' 1>&2
if ! PATH="$newpath" DEBOOTSTRAP_DIR="$tmp" $FAKEROOT \
"$tmp/debootstrap" --foreign --extractor='ar' --arch="$ARCH" \
"$RELEASE" "$tmp/$subdir" "$MIRROR" 1>&2; then
echo "debootstrap error log:" 1>&2
tail -n 3 "$tmp/$subdir/debootstrap/debootstrap.log" 1>&2 || true
error 1 'Failed to run debootstrap.'
fi
Maybe @TomTravis or @DennisLfromGA can help here.
A month later and after trying all suggestions posted here, I still cannot get crouton to work. Still getting the Failed to run debootstrap error.
Downloading bootstrap files... /tmp/crouton-installer-cache/crouton: 95: /tmp/crouton-installer-cache/crouton.cyv/installer/ubuntu/bootstrap: /tmp/crouton.K2R/debootstrap: Permission denied debootstrap error log: tail: cannot open '/tmp/crouton.K2R/xenial-amd64/debootstrap/debootstrap.log' for reading: No such file or directory Failed to run debootstrap.
I am running all commands as sudo. I would really like to get out of having to use Crostini for linux and get back to using Crouton for Linux. Are there anymore suggestions that I can follow or an eta of when this issue will be fixed??
I found the issue is caused by ChromeOS upgrade. It may be started from v107. There is some security and permission change. The script on /tmp cannot be executed anymore even remount /tmp to allow executable. But I don't know how to fix it.
anyone found fix?
anyone found fix?
Do you read last line of @dinoswong reply?
The problem is that tmpfs mounts in ChromeOS are now noexec, so you can't drop a script in /tmp and execute it (which breaks the bootstrap script), and /usr/local/ is mounted nodev, so the installer script needed changes.
My latest code at https://github.com/myelin/crouton is working for me right now; can you give it a try? I spent some time on it today and it can create sid, focal, jammy, and kinetic chroots on my brya machine running a personal 108.0.5355.0 build.
Note that startxfce4 currently fails on sid, jammy, and kinetic, but works on focal, so you probably want to use focal rather than any of the newer distributions.
The problem is that tmpfs mounts in ChromeOS are now noexec, so you can't drop a script in /tmp and execute it (which breaks the bootstrap script), and /usr/local/ is mounted nodev, so the installer script needed changes.
My latest code at https://github.com/myelin/crouton is working for me right now; can you give it a try? I spent some time on it today and it can create sid, focal, jammy, and kinetic chroots on my brya machine running a personal 108.0.5355.0 build.
Note that startxfce4 currently fails on sid, jammy, and kinetic, but works on focal, so you probably want to use focal rather than any of the newer distributions.
perfect! i try it tomorrow
The problem is that tmpfs mounts in ChromeOS are now noexec, so you can't drop a script in /tmp and execute it (which breaks the bootstrap script), and /usr/local/ is mounted nodev, so the installer script needed changes.
My latest code at https://github.com/myelin/crouton is working for me right now; can you give it a try? I spent some time on it today and it can create sid, focal, jammy, and kinetic chroots on my brya machine running a personal 108.0.5355.0 build.
Note that startxfce4 currently fails on sid, jammy, and kinetic, but works on focal, so you probably want to use focal rather than any of the newer distributions.
i keep getting this when entering my chroot Entering /mnt/stateful_partition/crouton/chroots/focal... /usr/local/bin/crash_reporter_wrapper: 119: exec: /var/run/crw/crw: Permission denied WARNING: Unable to register core dump handler. dbus[5292]: Unknown username "whoopsie" in message bus configuration file
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.20.13
X Protocol Version 11, Revision 0
Build Operating System: linux Ubuntu
Current Operating System: Linux localhost 5.10.147-20137-gfa8e6d1d4794 #1 SMP PREEMPT Sun Oct 16 23:14:38 PDT 2022 aarch64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure drm.trace=0x106 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 5324800 verity payload=PARTUUID=9dfac76e-a780-4c56-9716-bbbd838df974/PARTNROFF=1 hashtree=PARTUUID=9dfac76e-a780-4c56-9716-bbbd838df974/PARTNROFF=1 hashstart=5324800 alg=sha256 root_hexdigest=a43d60da85bd4fac5e2fb4b3ad514e11624e3d817e6028c427f3481d584c4d17 salt=03f0628d51731be6789698004606f2432bd1c5fce172c5bda24f6be93504eec6" noinitrd vt.global_cursor_default=0 kern_guid=9dfac76e-a780-4c56-9716-bbbd838df974 cpuidle.governor=teo
Build Date: 06 July 2022 01:53:24PM
xorg-server 2:1.20.13-1ubuntu1~20.04.3 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Fri Oct 21 11:48:40 2022
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.LibCrosService was not provided by any .service files
method return time=1666367320.665477 sender=:1.308 -> destination=:1.819 serial=15633 reply_serial=2
boolean true
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
(EE) event8 - Google Inc. Hammer: libinput bug: Internal or external? Please file a bug.
(EE) event8 - Google Inc. Hammer: libinput bug: Internal or external? Please file a bug.
crouton: version 1-20221017235132~main:0f39a42b
release: focal
architecture: arm64
xmethod: xorg
targets: gnome
host: version 15183.8.0 (Official Build) dev-channel kukui
kernel: Linux localhost 5.10.147-20137-gfa8e6d1d4794 #1 SMP PREEMPT Sun Oct 16 23:14:38 PDT 2022 aarch64 aarch64 aarch64 GNU/Linux
freon: yes
Running exit commands...
/usr/bin/xinit: connection to X server lost
Hangup
waiting for X server to shut down Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.LibCrosService was not provided by any .service files method return time=1666367329.520237 sender=:1.308 -> destination=:1.821 serial=15645 reply_serial=2 boolean true (II) Server terminated successfully (0). Closing log file.
Unmounting /mnt/stateful_partition/crouton/chroots/focal... and it doesnt boot it just shuts down
yes chromeOS updates have changed permissions and privs for files system /var /tmp /media / sudo mount -o remount,symfollow,exec /var* /tmp* /media* /* all need exec mounts
Shell now asked for password on sudo in shell the UID and PID are not tracked to well in Crouton chroot is it own FS and processes. ChromeOS tracks UID and PID better now My share "MyFiles" Download will no longer mount the icon on Desktop is gone the folder is present today for some reason i now using bullseye and bookworm
I now use a X86 M900 lenovo(not chroot) for FS bookworm and work general the chroots CB has issue but still works x2go work just fine over the next TB is storage and fast processor Mate and KDE desktops
it seems the X86 CB is supported different then arm CB this is reason for the m900 X86_64 intel
I really like the arm64 mediatek it run with less power and it performs very good W: Failure while configuring required packages. W: See //debootstrap/debootstrap.log for details (possibly the package usrmerge is at fault) Failed to complete chroot setup. Unmounting /media/removable/sd200/chroots/bookworm... Bookworm fails to load core chroot today ?
Your code worked! Thank you so much!
On Tue, Oct 18, 2022 at 3:05 AM Phillip Pearson @.***> wrote:
The problem is that tmpfs mounts in ChromeOS are now noexec, so you can't drop a script in /tmp and execute it (which breaks the bootstrap script), and /usr/local/ is mounted nodev, so the installer script needed changes.
My latest code at https://github.com/myelin/crouton is working for me right now; can you give it a try? I spent some time on it today and it can create sid, focal, jammy, and kinetic chroots on my brya machine running a personal 108.0.5355.0 build.
Note that startxfce4 currently fails on sid, jammy, and kinetic, but works on focal, so you probably want to use focal rather than any of the newer distributions.
— Reply to this email directly, view it on GitHub https://github.com/dnschneid/crouton/issues/4803#issuecomment-1281906692, or unsubscribe https://github.com/notifications/unsubscribe-auth/AX7SNVIBKHG7IKAPW6RIEU3WDZD2VANCNFSM6AAAAAAQIFI4OU . You are receiving this because you were mentioned.Message ID: @.***>
@TomTravis
chronos@localhost / $ sudo mount -o remount,symfollow,exec /var* /tmp* /media* /* mount: bad usage Try 'mount --help' for more information.
How to fix that???
Please re-open this. I still get the error and nothing in the thread seems to fix it...
It isnt working for me too. I didnt fixed it
#4878 this helped me a lot
The original issue is fixed in the latest crouton, so please try it again.
Okay I will try it again todqy