-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Xephyr cannot open host display #18
Comments
That's not good.
You may want to do a sanity check on the host Xauthority once you're inside the chroot |
The modification time was correct.
resets X and writes the following to STDERR:
|
Are you running from a crosh shell or from VT2? |
VT2. Should I be doing it from crosh? |
Definitely. The X11 server on ARM loooooves to crash. |
That was the problem. I'm new to chromebooks so "open a shell" in The Easy Way step 2 was a little too ambiguous for me. I'm guessing gregnwosu in issue #17 made the same mistake. Thank you very much. Your responses were incredibly quick. |
Awesome; glad that's the issue. I'll add a note in the README. |
Im having the same problem but on crosh (i have some problem almost every other time my chromebook updates usually I can fix it though) samsung chromebook orignial using kde not xfce4 |
I have the same problem ("Xephyr cannot open host display. Is DISPLAY set?") on a Samsung Chromebook arm, using a trusty crouton with lxde installed quite a while ago (before recent updates). I can log into the chroot but not start up lxde. From inside the chroot, I can still not start lxde, but there it gives a different error
I created another crouton (precise-lxde). This one works, I can log in and the GUI will start. I tried to update the trusty chroot, which seems to fail (I dunno whether that's what causes this issue):
|
(just coming back to note that the problem was that the updating kept crashing, because of issues with dependencies, and libraries pulled from non-standard sources. Once I resolved/removed those issues, the update went through and the GUI desktop works again.) |
I'm having the same issue as described in issue #17. I've reinstalled the chroot 3 times over the past few weeks with fresh crouton scripts, with no success.
sudo startxfce4 2>&1 | tee startxfce4.log
startxfce4.log:
/usr/bin/startxfce4: Starting X server
XIO: fatal IO error 2 (No such file or directory) on Xserver ":0" after 39 requests (39 known processed) with 0 events remaining.
Starting Xephyr manually results in the following:
export DISPLAY=:0
Xephyr :0 -fullscreen -ac
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.XO-lock and start again.
export DISPLAY=:1
Xephyr :1 -fullscreen -ac
Xephyr cannot open host display. Is DISPLAY set?
Googling this error makes it seem to be a .Xauthority issue.
I tried the solution on the Debian wiki http://wiki.debian.org/XStrikeForce/FAQ#howtoxnest
with no preliminary success.
The text was updated successfully, but these errors were encountered: