crouton
crouton copied to clipboard
Cant run a chroot without it crashing
name: unity
encrypted: yes, unlocked
Entering /mnt/stateful_partition/crouton/chroots/unity...
crouton: version 1-20220111101058~master:a9eafaee
release: impish
architecture: amd64
xmethod: xorg
targets: unity
host: version 14695.85.0 (Official Build) stable-channel octopus
kernel: Linux localhost 4.14.254-19064-g577a877aa35d #1 SMP PREEMPT Wed May 25 19:32:47 PDT 2022 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Not unmounting /mnt/stateful_partition/crouton/chroots/unity as another instance is using it.
name: xenial
encrypted: yes, locked
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
Please describe your issue:
I made a new chroot that is xenial and unity with the command
sudo crouton -e -t unity -r xenial When I open the chroot everything looks ok, but when I click the desktop or run an application I this happens
also it appears to be installing impish even when I explicitly tell it to install xenial. This same thing happens whenever I try to run impish, it always crashes
If known, describe the steps to reproduce the issue:
- Make a new chroot with
sudo crouton -e -t unity -r xenial or
- click on the desktop
Possible duplicate of #4368? Also, it appears you have two chroots (One with the name "unity" and another with "xenial").
Ok so I ran it again and I could run it just fine but upon switching back to chromeos it crashed again with this error
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.LibCrosService was not provided by any .service files
Ok so I ran it again and I could run it just fine but upon switching back to chromeos it crashed again with this error
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.LibCrosService was not provided by any .service files
So, this is the same error that I got in the previously linked issue, although there tends to be a little bit more to the message than just that part, is it like that for you?
check the file system if on a sdcard crosh > shell
sudo umount /dev/***** sudo fsck /dev/***** reply fix? a when clean remount exec and symfollow delete some chroots and try again most of my chroots need fsck daily on external FS
sudo fsck /dev/*****
when I do this it says
fsck: too many devices
mmcblk1 179:64 0 183.3G 0 disk / zram0 252:0 0 5.5G 0 disk [SWAP] (wrk)coco@localhost:/usr/local/bin$ df df: /home/coco/.cache/doc: Operation not permitted Filesystem 1K-blocks Used Available Use% Mounted on /dev/mmcblk1 189234312 113067328 66538008 63% / yes fsck 1 dev at a time at shell no chroot open