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

Xorg X11 servers cannot be launched from Frecon, return to Chromium OS and use Crosh to launch X #5037

Closed
Somethingidk1 opened this issue Dec 16, 2023 · 2 comments

Comments

@Somethingidk1
Copy link

Somethingidk1 commented Dec 16, 2023

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

Can't because of the error constantly terminating the connection to the chroot

Please describe your issue:

Sudo is disabled in the Crosh shell after about R119, fixed that by using the VT2 shell, auto tools has been removed, fixed that by using CROSH_BRANCH=silence, now the error described in the title shows up whenever I try sudo startgnome or sudo enter-chroot startgnome

If known, describe the steps to reproduce the issue:

Have a Lenovo IdeaPad Duet without the keyboard pack, with a USB-C dongle and a wired iMac keyboard and wireless mouse and the worst timing to try Crouton in the world.

@Somethingidk1 Somethingidk1 changed the title Xorg X11 servers cannot be launched from Frecon Xorg X11 servers cannot be launched from Frecon, return to Chromium OS and use Crosh to launch X Dec 16, 2023
@Somethingidk1
Copy link
Author

It also happens whenever I try anything with -chroot at the end (edit-chroot, enter-chroot, etc.) but not when I use delete-chroot.

Tried all desktop environments and I am not skilled enough for not using them. Unity and Unity-Desktop do not work because I am trying to use Xenial and the last arm-based build of Unity was for Precise.

@akang22
Copy link

akang22 commented Jan 5, 2024

See #5013. You can't open x11 servers from the vt2 shell.

You can use the workaround in the link (sshing into the vt2 terminal from your crosh and then starting your gnome).

What I'm (trying to) do is just use an old version of ChromeOS and disable updates, because (to me) even if the existing solution works crouton is in maintenance mode (so I don't necessarily know what future changes ChromeOS could make to break crouton; not a knock on the wonderful creators of crouton). However I can't seem to get around the auto tools issue, even when using silence branch, but if I get it working I'll keep you posted.

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