Skip to content
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

help: edit chroot to target bionic, instead of unity #4963

Closed
Essen73 opened this issue Apr 11, 2023 · 3 comments
Closed

help: edit chroot to target bionic, instead of unity #4963

Essen73 opened this issue Apr 11, 2023 · 3 comments

Comments

@Essen73
Copy link

Essen73 commented Apr 11, 2023

Please paste the output of the following command here: sudo edit-chroot -all

name: xenial
encrypted: yes, locked
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

Please describe your issue:

I did do-release upgrade using the Ubuntu command line and upgraded to bionic from xenial
bionic was working but seemed a bit unstable, for example google maps kept crashing; so decided to logout and restart
while logging back in to Ubuntu using sudo startunity, realized that I needed to change 'startunity' to some other target specific to bionic
I am stuck at this step - how do I edit chroot to work with the bionic ubuntu

If known, describe the steps to reproduce the issue:

@ducksosu
Copy link

ducksosu commented Apr 11, 2023

@Essen73 while using xfce i have had no issues with crashing on bionic

if you want to install xfce (or any other target) just do 'sudo crouton -u -n chrootname -t xfce'

and then you can use either sudo startxfce4 to run using xfce or sudo startunity to run using unity

@Essen73
Copy link
Author

Essen73 commented Apr 12, 2023

@ducksosu That's awesome; it worked; with the xfce I can access all my previous files in libreoffice etc. Thanks. The unity path does not work, but thats OK. I now need to understand how chroot works; although I am creating a new chroot, how is it finding and connecting to my previous linux environment etc...

@ducksosu
Copy link

your welcome! (you should probably close the issue since its no longer an issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants