Crouton: Can't run prepare.sh during setup, and can't access file when run separately

[thatlittlegit]

chronos@localhost ~ $ sudo edit-chroot -all
name: artful
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/artful...
ln: failed to access '/var/run/crouton/mnt/stateful_partition/crouton/chroots/artful/etc/resolv.conf': Permission denied
Unmounting /mnt/stateful_partition/crouton/chroots/artful...

Please describe your issue:

I can't start any chroot on any version. It seems to be complaining about permission denied, which makes no sense as I am root. When setting up the chroot, it can't run prepare.sh. This also happened on a chroot which worked consistantly for several weeks. As

If known, describe the steps to reproduce the issue:

chronos@localhost ~/Downloads $ sudo sh crouton -t cli-extra
...
Installing crash_report_wrapper into the host...
chroot: failed to run command '/prepare.sh': Permission denied
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
chronos@localhost ~/Downloads $ sudo enter-chroot
Entering /mnt/stateful_partition/crouton/chroots/xenial...
A chroot setup script still exists inside the chroot.
The chroot may not be fully set up.
Would you like to finish the setup? [Y/n/d] y
Preparing chroot environment...
ln: failed to access '/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/etc/resolv.conf': Permission denied
The chroot setup script may be broken. Your chroot is not fully configured.
Removing the chroot setup script. You may want to update your chroot again.
/mnt/stateful_partition/crouton/chroots/xenial doesn't appear to be a valid chroot.
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

/mnt/stateful_partition/crouton/chroots/xenial/etc/resolv.conf also seems to be a broken symlink:

lrwxrwxrwx. 1 root root 27 Mar 24 12:57 /mnt/stateful_partition/crouton/chroots/xenial/etc/resolv.conf -> /var/host/shill/resolv.conf

(the filenames highlighted in red)

Thanks for any help :+1:

EDIT: My CrOS version is Version 67.0.3376.0 (Official Build) canary (32-bit)

[DennisLfromGA]

@thatlittlegit,

It seems to be complaining about permission denied, which makes no sense as I am root.

Sometimes permissions can get set incorrectly when you become 'root' in your chroot profile.
To fix it, if it happens, you can do the following:

sudo enter-chroot -n artful
sudo chown -R 1000:1000 "$HOME"
exit

You can also request that enter-chroot run the setup script by using the '-xx' option, see below:

    -x          Does not log in, but directly executes the command instead.
                Note that the environment will be empty (sans TERM).
                Specify -x a second time to run the /prepare.sh script.

If none of that helps then you can try to repair things with a crouton update:

• sudo sh ~/Downloads/crouton -n artful -u

Hope this helps,
-DennisLfromGA

[thatlittlegit]

Unfortunately, those didn't work. Here's the outputs:

(note: using xenial because I deleted artful)

chronos@localhost ~ $ sudo enter-chroot -n xenial
/mnt/stateful_partition/crouton/chroots/xenial doesn't appear to be a valid chroot.
chronos@localhost ~ $ sudo enter-chroot -xx
ln: failed to access '/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/etc/resolv.conf': Permission denied
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
chronos@localhost ~ $ sudo sh Downloads/crouton -n xenial -u
/usr/local/chroots/xenial already exists, updating it...
Preparing chroot environment...
...
ln: failed to access '/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/etc/resolv.conf': Permission denied
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
chronos@localhost ~ $ echo $?
1

I also just tried chrooting into /usr/local/chroots/xenial, and despite the permissions it says it can't run /bin/bash. Any suggestions?

[DennisLfromGA]

@thatlittlegit,

Any suggestions?

No more than what I listed above I'm afraid.

My resolve.conf file has the exact permissions as yours so I think that link error is just a product of the condition of your chroot. -

ln: failed to access '/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/etc/resolv.conf': Permission denied
The chroot setup script may be broken. Your chroot is not fully configured.
Removing the chroot setup script. You may want to update your chroot again.
/mnt/stateful_partition/crouton/chroots/xenial doesn't appear to be a valid chroot.

That last statement indicates it's pretty broken I'm afraid.
My only additional suggestion is to delete that chroot and start over if you haven'y invested too much in it.

Hope this helps,
-DennisLfromGA

[thatlittlegit]

That's weird. The xenial chroot was made when I made the question. My main chroot (which got deleted, and I copied the files off of) was made a few weeks before this question, and stopped working a few days ago. I suppose this means something happened in the generation process and to my existing chroot?

[DennisLfromGA]

@thatlittlegit,

I suppose this means something happened in the generation process and to my existing chroot?

Could be I guess, sometimes even a Chrome OS update can cause issues, sometimes it's just hard to tell what happened.

I've tried to move or copy chroots to / from external media and occasionally things get hosed for no apparent reason. A lot of times I'll just try to make a list of my installed packages and copy my $HOME files & settings and start anew. It's usually much quicker than trying to fix it.

Hope this helps,
-DennisLfromGA

[toothrot]

Hi @thatlittlegit, I had the same issue in #3688 (comment after the close). It started happening once I switched to the Canary channel. Are you on Canary as well?

[thatlittlegit]

Yes, I'm on Canary.

[SimpleWolf]

I'm not on the Canary Channel and I just got this exact issue :L

[zareki]

I am having these same issue.

I changed the channel with no avail.

I disable developer mode, factory reset the chromebook and proceded to reinstall crouton with the same results.

[malkia]

@DennisLfromGA - Also duplicate is https://github.com/dnschneid/crouton/issues/3702

[beaufortfrancois]

@dnschneid Do you have any idea what is happening there?

[efundz1]

even tried deleting the chroot and adding a new chroot to no avail, this all stemmed following a recent update.

awaiting suggestions and recommendations

many thanks

[SimpleWolf]

It certainly has something to do with the update messing up the permissions

[AlexBigCheese]

does anyone know what the original resolv.conf looked like?

[tedb]

Hi, this broke for me after my Chromebook updated to Version 67.0.3376.0 (Official Build) dev (64-bit) (it's on the Dev channel).

In short, it looks like permissions got broken pretty badly for Crouton. As root on the host, I replaced the chroot's symlink for /etc/resolv.conf with a copy of the host system's file, but now I get a new error. Details below.

Just guessing, this smells like ChromeOS might be applying new security policies, like SELinux or similar, that are interfering here.

chronos@localhost ~/Downloads $ sudo -i
Password: 

localhost ~ # cd /mnt/stateful_partition/crouton/chroots/sid/etc

localhost /mnt/stateful_partition/crouton/chroots/sid/etc # ls -l resolv.conf
lrwxrwxrwx 1 root root 27 Mar 27 09:34 resolv.conf -> /var/host/shill/resolv.conf
# Note, the symlink of the target was flashing red here, I assume because the path doesn't exist in the host environment

localhost /mnt/stateful_partition/crouton/chroots/sid/etc # rm resolv.conf

localhost /mnt/stateful_partition/crouton/chroots/sid/etc # cp /etc/resolv.conf .

localhost /mnt/stateful_partition/crouton/chroots/sid/etc # ls -l resolv.conf
-rw-r--r-- 1 root root 67 Mar 27 09:38 resolv.conf

localhost /mnt/stateful_partition/crouton/chroots/sid/etc # cat resolv.conf
nameserver 192.168.1.1
options single-request timeout:1 attempts:5

localhost /mnt/stateful_partition/crouton/chroots/sid/etc # enter-chroot -n sid
Entering /mnt/stateful_partition/crouton/chroots/sid...
chroot: failed to run command 'su': Permission denied
WARNING: starting chroot system dbus daemon failed with code 126
chroot: failed to run command 'su': Permission denied
Unmounting /mnt/stateful_partition/crouton/chroots/sid...

localhost /mnt/stateful_partition/crouton/chroots/sid/etc # 

[tedb]

Even creating a new chroot fails with chroot: failed to run command '/prepare.sh': Permission denied:

```
chronos@localhost ~/Downloads $ sudo sh crouton -t cli-extra -n new
Installing xenial-amd64 chroot to /usr/local/chroots/new
Downloading latest debootstrap...
...
I: Extracting util-linux...
I: Extracting zlib1g...
Moving bootstrap files into the chroot...
Preparing chroot environment...
Installing brightness into the chroot...
Installing croutonpowerd into the chroot...
Installing croutonversion into the chroot...
Installing host-dbus into the chroot...
Installing host-wayland into the chroot...
Installing startcli into the host...
Installing croutonpowerd into the chroot...
Installing enter-chroot into the host...
Installing delete-chroot into the host...
Installing edit-chroot into the host...
Installing mount-chroot into the host...
Installing unmount-chroot into the host...
Installing crash_reporter_wrapper into the host...
chroot: failed to run command '/prepare.sh': Permission denied
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/new...

[DictatorBob]

After the version 67 update (which landed yesterday for me on my Pixelbook), my chroots are unusable as well.

I notice that within the chroot, /etc/resolv.conf is currently a broken symlink:

localhost /mnt/stateful_partition/crouton/chroots/stretch/etc # ls -l resolv.conf 
lrwxrwxrwx. 1 root root 27 Mar 26 15:53 resolv.conf -> /var/host/shill/resolv.conf

/var/host doesn't currently exist anywhere.

Manually changing that symlink to point to (for example) /var/run/shill/resolv.conf (which exists)
does not solve the problem. Still get a permission denied error, and I suspect there's more to this.

[janhaa]

Same here.

[dnschneid]

Apologies for the slow response here. I'm working on a patch for this -- turns out the symlink traversal restrictions that were put in place in 67 affect crouton a bit more than I expected. If you have an encrypted chroot, everything should just work, but unencrypted chroots are subject to the symlink restrictions by default and won't work. The resolv.conf error is one (silly) manifestation of this restriction, as well as the failure to run /prepare.sh or even /bin/sh...

[dnschneid]

OK, pushed a fix. Please try out the latest crouton and see if things work on 67.

[efundz1]

Tried with the new crouton, deleted the old chroot, however still no joy with starting lxde and still getting the permission denial with /prepare.sh

[DennisLfromGA]

@efundz1,

Can you please show us the output of: sudo edit-chroot -all

-DennisLfromGA

[efundz1]

as requested

chronos@localhost / $ sudo edit-chroot -all
name: xenial encrypted: no Entering /mnt/stateful_partition/crouton/chroots/xenial... chroot: failed to run command '/usr/local/bin/croutonversion': Permission denied Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

[DennisLfromGA]

@efundz1,

Tried with the new crouton ...

Not sure if you mean you just downloaded a new crouton installer or what exactly.

Did you try to update an existing chroot or install a new one?

-DennisLfromGA

[efundz1]

sorry, let me clarify, i downloaded the new crouton, deleted and reinstalled the new chroot which generated the output above

[dnschneid]

Just as a sanity check, could you please run: md5sum /usr/local/bin/mount-chroot

The output should be:
d30c4c90b4057a3e6190c1b6c5a6ccdc /usr/local/bin/mount-chroot if you have the latest crouton.

[DictatorBob]

Same result for me. I tried an update of the chroot, not a brand new one. The result of that was:

chroot: failed to run command 'su': Permission denied
WARNING: starting chroot system dbus daemon failed with code 126
chroot: failed to run command 'su': Permission denied
Unmounting /mnt/stateful_partition/crouton/chroots/stretch...

See below for edit-chroot and md5sum output.

chronos@localhost ~ $ sudo edit-chroot -all
Password: 
name: stretch
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/stretch...
chroot: failed to run command '/usr/local/bin/croutonversion': Permission denied
Unmounting /mnt/stateful_partition/crouton/chroots/stretch...
chronos@localhost ~ $ md5sum /usr/local/bin/mount-chroot
d30c4c90b4057a3e6190c1b6c5a6ccdc  /usr/local/bin/mount-chroot

[dnschneid]

OK, clearly this isn't fixed yet. Let me look into it some more...

[efundz1]

chronos@localhost / $ md5sum /usr/local/bin/mount-chroot

Output d30c4c90b4057a3e6190c1b6c5a6ccdc /usr/local/bin/mount-chroot

rgds
Jim

[dnschneid]

Oooookay. Try again. I think I scraped all the failsauce off of the previous commit.

[zareki]

Using the stable channel after power wash from beta channel fixed the issue
for me (without using the new crouton)

On Tue, Mar 27, 2018 at 7:20 PM, David Schneider [e-mail]
wrote:

Oooookay. Try again. I think I scraped all the failsauce off of the
previous commit.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3695#issuecomment-376707091,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANGCa38xUtumLp9dol4xMBMksjejz2aSks5tislOgaJpZM4S50IJ
.

[Im-Ian-Chen]

it work after pushing a fix,thanks!!!

[dnschneid]

@zareki: sure, dev channel will always break several weeks before stable.

@cjzlol: awesome, thanks for confirming.

[efundz1]

Seems to be working

thanks
Jim

-=-

On Wed, Mar 28, 2018 at 12:54 AM, David Schneider [e-mail]
wrote:

@zareki https://github.com/zareki: sure, dev channel will always break
several weeks before stable.

@cjzlol https://github.com/cjzlol: awesome, thanks for confirming.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3695#issuecomment-376712966,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVk0vzWjGFCWbkFxfL-ORXki9atuA2egks5titEvgaJpZM4S50IJ
.

[DictatorBob]

Works for me, I ran a "sudo sh ./crouton -u -n stretch" and then a "sudo enter-chroot" and all seems to be working. Thanks a bunch, your work is greatly appreciated. :)

[rheinandco]

Hello,
I have the same problem:
Version 67.0.3376.0 (Build officiel) dev (64 bits) and when I start Crouton I get this message:
chronos@localhost / $ sudo startxfce4
Entering /mnt/stateful_partition/crouton/chroots/xenial...
ln: failed to access '/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/etc/resolv.conf': Permission denied
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
I'm not a specialist. Could you please tell me what to do to access again to my Xenial?
Thank you

[DennisLfromGA]

@rheinandco,

I answered your G+ post but I'll do it here too and offer a few more suggestions.

1. Reboot
2. Run: sudo sh ~/Downloads/crouton -n xenial -u
3. Try: sudo startxfce4

If that doesn't work let us know here so we can help you further.

Hope this helps,
-DennisLfromGA

[beaufortfrancois]

It works like a charm now! Thank you @dnschneid

1. Download latest version of Crouton at https://goo.gl/fd3zc
2. Open Shell
3. sudo sh ~/Downloads/crouton -u -n name where name is the name of your chroot
4. sudo enter-chroot name
5. Enjoy!

[rheinandco]

@DennisLfromGA It works again! Thank you for your quick answer... Can work again! :-)

[sadams0]

Hi,
I hit this problem this morning (in the UK).
Many thanks to others here for reporting it, documenting it and of course to Mr David Schneider for getting a fix out so quickly.
I've come to rely on Crouton now and it's a serious hit to productivity if it breaks.

Any comment on these rumours of something more official/supported coming?
https://chromeunboxed.com/news/chromebook-containers-virtual-machine-crostini-google-io

Thanks again, efforts appreciated, Steve.

[SimpleWolf]

<3

[heyypatrick]

Bumped into this issue today. Now fixed. Thanks @beaufortfrancois @dnschneid

[thatlittlegit]

Just tried making a new chroot. It failed to create the folders (.../bin, .../debootstrap, etc.), but running mkdir with all of them and restarting the chroot creation process works like a charm. Not sure if that needs to be a separate issue - at least it has a clear workaround.

Thanks @dnschneid!

[F1k1pho3n1x]

Downloading the latest version of Crouton seems to have done the trick!

Thanks so much for the fix!

Stay amazing! <3

[huynle]

AMAZING! thank you so much for this

[AverageBunny]

I am having problems with this as well. Can anyone help me? Whenever I try to launch into unity by using the command, 'sudo startunity', I get the output,
'Entering /mnt/stateful_partition/crouton/chroots/xenial...'
'ln: failed to access 'var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/etc/resolv.conf ': Permission denied'
'Unmounting /mnt/stateful_partition/crouton/chroots/xenial..."

[jonchurch]

Thanks everyone! Was quite worried when I saw this error today, as my chromebook is my main development machine (been running a Toshiba 2, the older model, for two years with crouton and a cli install of ubuntu). To reiterate what was stated above in this thread, my steps to fix were the following.

Note, this did NOT delete or reinstall my chroot! So no worries there folks about losing your data.

• If you have the crouton executable in your Downloads folder still, open up a terminal, enter shell mode by typing shell and then run the following:

sudo sh ~/Downloads/crouton -u -n <your chroot 's name>

The -u flag updates crouton and your chroot, and the -n flag is the chroot you'd like to update. Crouton will download the latest version of the crouton script by itself, so no worries there.

• If you do not have the crouton script on your system anymore for whatever reason, follow the link posted above https://goo.gl/fd3zc to get the script and then run the above command. This will update your chroot and things should be smooth sailing after that!

Thanks again everybody, I love this project and am very pleased the community is so supportive!

[grafer74]

@beaufortfrancois
It worked perfectly for me.
Many thanks!

[MarkSDS]

Updating my Elementary from shell did it for me, as suggested by @DennisLfromGA in
https://github.com/dnschneid/crouton/issues/3695 👍

chronos@localhost / $ sudo sh ~/Downloads/crouton -n elementary -u

[jasonmhite]

A note for people coming across this issue, the command should be

sudo sh ~/Downloads/crouton -n <...> -u

i.e. the -u goes at the end. I was confused for a minute reading through some of the earlier posts,.

[DennisLfromGA]

@jasonmhite,

EDIT:
~Some clarification: the '-u' option is necessary but it doesn't have to be at the end.~
Sorry, that did not clarify much at all.

I'll take another shot and try to explain it better -

The '-u' option is used with the crouton script/command for updating your chroot.
That means it should come after the ... ~/Downloads/crouton part of that command string.
It does not belong after the sudo or after sh in that command string since it would the be applied to those commands.

So, placing '-u' at the end of the command is perfectly logical and an excellent choice.

Hopefully that clears up any misunderstanding about where to use crouotn's '-u' update option.

Hope this helps,
-DennisLfromGA

[jasonmhite]

It did for me, does not work if -u comes at the beginning.

On Mon, Jul 9, 2018 at 5:16 PM DennisL [e-mail] wrote:

@jasonmhite https://github.com/jasonmhite,

Some clarification: the '-u' option is necessary but it doesn't have to
be at the end.

Hope this helps,
-DennisLfromGA

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3695#issuecomment-403623061,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1BcoVdJfk0bdcOldCTIQak0rJY3HLeks5uE8gigaJpZM4S50IJ
.

[lucash731]

thank you, sudo sh ~/Downloads/crouton -u -n worked.

[atersol]

I'm having the same problem as others. What need I do to get this to work.

After downloading a new crouton from the link referenced,
I tried "sudo sh ~/Downloads/crouton -n trusty -u"
Installation proceeds until
"dpkg: dependency problems prevent configuration of bbcb:
bbcb depends on libgtk2.0-0:i386.
bbcb depends on libgnomeui-0:i386.
bbcb depends on gtk2-engines:i386.
bbcb depends on gtk2-engines-murrine:i386.
bbcb depends on libcanberra-gtk-module:i386.
bbcb depends on libgnomeui-0:i386.
bbcb depends on gnome-icon-theme-full:amd64; however:
Package gnome-icon-theme-full is not installed.

dpkg: error processing package bbcb (--configure);
dependency problems - leaving unconfigured
Errors were encountered while processing:
bbcb
Failed to complete chroot setup
Unmounting /mnt/stateful_partition/crouton/chroots/trusty...
Sending SIGTERM to processes under /mnt/stateful_partition/crouton/chroots/trusty..."

[DennisLfromGA]

@atersol,

"dpkg: dependency problems prevent configuration of bbcb:

Try getting back into your chroot with:

• sudo enter-chroot -n trusty

When it asks if you want to run the setup script enter 'n'
It will leave you in a shell session in the chroot.
Then run the following to try and fix the broken package(s):

• sudo apt-get -f install

When that completes successfully exit the chroot and then run the update command again.

Hope this helps,
-DennisLfromGA

[atersol]

Thanks. Did that and got to place where I can boot into Ubuntu from
crosh. Seems that Unity isn't working correctly - there are no close
controls on the windows, and it doesn't have the Launcher. I'm pursuing
some suggestions from StackExchange -
https://askubuntu.com/questions/475296/unity-launcher-and-top-panel-disappeared-in-14-04

Making progress. Thanks.
Antony Tersol

On Sat, Aug 25, 2018 at 8:47 PM DennisL [e-mail] wrote:

@atersol https://github.com/atersol,

"dpkg: dependency problems prevent configuration of bbcb:

Try getting back into your chroot with:

• sudo enter-chroot -n trusty

When it asks if you want to run the setup script enter 'n'
It will leave you in a shell session in the chroot.
Then run the following to try and fix the broken package(s):

• sudo apt-get -f install

When that completes successfully exit the chroot and then run the update
command again.

Hope this helps,
-DennisLfromGA

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3695#issuecomment-416011776,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXlYKoHKaUDpTOsaAuE4Pa07dBj9Kwh6ks5uUhpJgaJpZM4S50IJ
.

[DennisLfromGA]

@atersol,

It's hard to tell what might be wrong with Unity.
You didn't show us the output of sudo edit-chroot -all so I don't know what you have installed.

If you haven't already you might try installing another desktop and see if that works for you.
Maybe try something like this:

• sudo sh ~/Downloads/crouton -n trusty -t lxde-desktop -u

The start it with:

• sudo startlxde -n trusty

Hope this helps,
-DennisLfromGA

[atersol]

I upgraded to Xenial, following the instructions at
https://github.com/dnschneid/crouton/wiki/Upgrade-chroot-release

output of sudo edit-chroot attached and copied here:

name: xenial
encrypted: no
crouton: version unknown
release: unknown
architecture: unknown
xmethod: xiwi
targets: unity,xiwi,extension
host: version 10718.71.2 (Official Build) stable-channel gandof
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Aug 1 21:16:04 PDT 2018
x86_64 x86_64 x86_64 GNU/Linux
freon: yes

I'm trying what you suggested as I write this (substituting xenial for
trusty))

Antony Tersol

On Sat, Aug 25, 2018 at 9:44 PM DennisL [e-mail] wrote:

@atersol https://github.com/atersol,

It's hard to tell what might be wrong with Unity.
You didn't show us the output of sudo edit-chroot -all so I don't know
what you have installed.

If you haven't already you might try installing another desktop and see if
that works for you.
Maybe try something like this:

• sudo sh ~/Downloads/crouton -n trusty -t lxde-desktop -u

The start it with:

• sudo startlxde -n trusty

Hope this helps,
-DennisLfromGA

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3695#issuecomment-416013675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXlYKq-nwHKMzquyXU1kBY2qbNRQ_JYCks5uUiezgaJpZM4S50IJ
.

name: xenial
encrypted: no
crouton: version unknown
release: unknown
architecture: unknown
xmethod: xiwi
targets: unity,xiwi,extension
host: version 10718.71.2 (Official Build) stable-channel gandof
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Aug 1 21:16:04 PDT 2018 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

[atersol]

Desktop still downloading.

Can you explain a little more? When I updated Trusty to Xenial, it was
downloading the linux kernal or some layer of files to execute Xenial on
top of ChromeOS, correct? Is the desktop a layer on top of that?

The download I am doing of lxde, is that just the desktop, or is it loading
another copy of xenial or ?

Antony Tersol

On Sat, Aug 25, 2018 at 10:03 PM Antony Tersol [e-mail] wrote:

I upgraded to Xenial, following the instructions at
https://github.com/dnschneid/crouton/wiki/Upgrade-chroot-release

output of sudo edit-chroot attached and copied here:

name: xenial
encrypted: no
crouton: version unknown
release: unknown
architecture: unknown
xmethod: xiwi
targets: unity,xiwi,extension
host: version 10718.71.2 (Official Build) stable-channel gandof
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Aug 1 21:16:04 PDT 2018
x86_64 x86_64 x86_64 GNU/Linux
freon: yes

I'm trying what you suggested as I write this (substituting xenial for
trusty))

Antony Tersol

On Sat, Aug 25, 2018 at 9:44 PM DennisL [e-mail] wrote:

@atersol https://github.com/atersol,

It's hard to tell what might be wrong with Unity.
You didn't show us the output of sudo edit-chroot -all so I don't know
what you have installed.

If you haven't already you might try installing another desktop and see
if that works for you.
Maybe try something like this:

• sudo sh ~/Downloads/crouton -n trusty -t lxde-desktop -u

The start it with:

• sudo startlxde -n trusty

Hope this helps,
-DennisLfromGA

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3695#issuecomment-416013675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXlYKq-nwHKMzquyXU1kBY2qbNRQ_JYCks5uUiezgaJpZM4S50IJ
.

[atersol]

After it finished, I am able to "sudo startlxde" and it works fine.
Now, I can also "sudo startunity" and the launcher is back, and the windows
have full functionality.

It's all working. Thanks for your help.

Antony Tersol

On Sat, Aug 25, 2018 at 10:18 PM Antony Tersol [e-mail] wrote:

Desktop still downloading.

Can you explain a little more? When I updated Trusty to Xenial, it was
downloading the linux kernal or some layer of files to execute Xenial on
top of ChromeOS, correct? Is the desktop a layer on top of that?

The download I am doing of lxde, is that just the desktop, or is it
loading another copy of xenial or ?

Antony Tersol

On Sat, Aug 25, 2018 at 10:03 PM Antony Tersol [e-mail] wrote:

I upgraded to Xenial, following the instructions at
https://github.com/dnschneid/crouton/wiki/Upgrade-chroot-release

output of sudo edit-chroot attached and copied here:

name: xenial
encrypted: no
crouton: version unknown
release: unknown
architecture: unknown
xmethod: xiwi
targets: unity,xiwi,extension
host: version 10718.71.2 (Official Build) stable-channel gandof
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Aug 1 21:16:04 PDT 2018
x86_64 x86_64 x86_64 GNU/Linux
freon: yes

I'm trying what you suggested as I write this (substituting xenial for
trusty))

Antony Tersol

On Sat, Aug 25, 2018 at 9:44 PM DennisL [e-mail] wrote:

@atersol https://github.com/atersol,

It's hard to tell what might be wrong with Unity.
You didn't show us the output of sudo edit-chroot -all so I don't know
what you have installed.

If you haven't already you might try installing another desktop and see
if that works for you.
Maybe try something like this:

• sudo sh ~/Downloads/crouton -n trusty -t lxde-desktop -u

The start it with:

• sudo startlxde -n trusty

Hope this helps,
-DennisLfromGA

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3695#issuecomment-416013675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXlYKq-nwHKMzquyXU1kBY2qbNRQ_JYCks5uUiezgaJpZM4S50IJ
.

[DennisLfromGA]

@atersol,

Very glad it worked out and you're back in business.

Can you explain a little more? When I updated Trusty to Xenial, it was
downloading the linux kernal or some layer of files to execute Xenial on
top of ChromeOS, correct?

It was downloading a newer version of Ubuntu, upgrading from 14.04 LTS (trusty) to 16.04 LTS (xenial).
crouton installs a Linux distro but it shares the Chrome OS kernel, audio, network, and other things and runs simultaneously with Chrome OS, in fact, it depends on it.

Is the desktop a layer on top of that?

In short, yes

The download I am doing of lxde, is that just the desktop, or is it loading
another copy of xenial or ?

Just the desktop and any applications/packages that come with it.
A 'desktop' is a GUi interface to or on top of the Ubuntu distro no matter what version.
There are many desktops available in crouton since users prefer different features and interfaces. You can get a list of them by entering: sudo sh ~/Downloads/crouton -t list

The above is just my rudimentary understanding of things and is in no way authoritative but I hope it helps.

Hope this helps,
-DennisLfromGA

[atersol]

Thanks for the help and explanation. I use Ubuntu primarily to run
LibreOffice and Blackbox Framework (a software development and delivery
platform, under Wine).

Antony Tersol

On Sun, Aug 26, 2018 at 9:11 AM DennisL [e-mail] wrote:

@atersol https://github.com/atersol,

Very glad it worked out and you're back in business.

Can you explain a little more? When I updated Trusty to Xenial, it was
downloading the linux kernal or some layer of files to execute Xenial on
top of ChromeOS, correct?

It was downloading a newer version of Ubuntu, upgrading from 14.04 LTS
(trusty) to 16.04 LTS (xenial).
crouton installs a Linux distro but it shares the Chrome OS kernel, audio,
network, and other things and runs simultaneously with Chrome OS, in fact,
it depends on it.

Is the desktop a layer on top of that?

In short, yes

The download I am doing of lxde, is that just the desktop, or is it loading
another copy of xenial or ?

Just the desktop and any applications/packages that come with it.
A 'desktop' is a GUi interface to or on top of the Ubuntu distro no matter
what version.
There are many desktops available in crouton since users prefer different
features and interfaces. You can get a list of them by entering: sudo sh
~/Downloads/crouton -t list

The above is just my rudimentary understanding of things and is in no way
authoritative but I hope it helps.

Hope this helps,
-DennisLfromGA

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3695#issuecomment-416049859,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXlYKpFrQb0bXcj8ntM7iT25gHcgktnMks5uUsirgaJpZM4S50IJ
.