Hallo Stefan,<br><br>i got the same result if i start xephyr <span style="font-weight: bold;">from inside</span> the scratchbox and thats your fault. <br><br>1. start xephyr script (in a normal shell)<br>2. login scratchbox
<br>3. export display<br>4. af-sb-init.start<br><br>That works.<br><br>br<br>Mathias<br><div><span class="gmail_quote">2007/6/23, Stefan Sassenberg <<a href="mailto:stefan.sassenberg@gmx.de">stefan.sassenberg@gmx.de</a>
>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Mathias Uebelacker schrieb:<br>> at first try export DISPLAY=IP:2, and resolve localhost (127....)
<br>><br>[sbox-X86: ~] > export DISPLAY=<a href="http://192.168.0.196:2">192.168.0.196:2</a><br>[sbox-X86: ~] > ./start-xephyr.sh<br><br>Xephyr cannot open host display. Is DISPLAY set?<br>[sbox-X86: ~] ><br><br>
This is not strange to me. Why should I export DISPLAY=IP:2 at that<br>point when my DISPLAY is at localhost:10.0? localhost:10.0 is the<br>display that Xephyr should *use*, while :2 is the display that Xephyr<br>*offers*. That's why tutorials ask me to
start-xephyr.sh and then<br>"export DISPLAY=:2" followed by af-sb-init.sh.<br><br>Top posting confuses me :-)<br><br>Stefan<br></blockquote></div><br>