[maemo-developers] [maemo-developers] problems using Xephyr

[From: kurt ak]

Hi all!
Is there a common reason why Xephyr has a hard time starting when I have the 
DISPLAY var set??  It seems to still not see this variable... below is what I do 
in the sandbox.  I have the same problem with af-sb-init.sh.

many thanks,
kurt



[sbox-SDK_PC: ~] > export DISPLAY=:2
[sbox-SDK_PC: ~] > echo $DISPLAY
:2
[sbox-SDK_PC: ~] > cat start-xephyr.sh
#!/bin/sh -e
prefix=/scratchbox/users/${LOGNAME}/targets/SDK_PC/usr
export LD_LIBRARY_PATH=${prefix}/lib; export LD_LIBRARY_PATH
exec ${prefix}/bin/Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac
[sbox-SDK_PC: ~] > ./start-xephyr.sh

Xephyr cannot open host display. Is DISPLAY set?

[sbox-SDK_PC: ~] > af-sb-init.sh start
Note: For remote X connections DISPLAY should contain hostname!
Sample files present.
DBUS system bus is already running, doing nothing
Starting D-BUS session bus daemon
Starting Maemo Launcher: maemo-launchermaemo-launcher[27651]: GLIB CRITICAL ** 
Gdk - gdk_display_close: assertion `GDK_IS_DISPLAY (display)' failed
.
Starting Sapwood image server
Starting Matchbox window manager
Starting clipboard-manager
Starting Keyboard
maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'
Starting MAEMO AF Desktop
maemo-launcher: invoking '/usr/bin/maemo_af_desktop.launch'
[sbox-SDK_PC: ~] > sapwood-server[27668]: GLIB WARNING ** Gdk - cannot open 
display: (null)
matchbox-wm: can't open display! check your DISPLAY variable.
Could not open display. Is the DISPLAY environment variable set?
maemo-launcher: child (pid=27697) exited due to signal=11
smaemo-launcher: no child 27720 found in the kindergarten.
maemo-launcher: child (pid=27720) exited due to exit()=0
maemo-launcher: child (pid=27714) exited due to signal=11
maemo-launcher: no child 27721 found in the kindergarten.
maemo-launcher: child (pid=27721) exited due to exit()=0