Hi,

I installed Scratchbox and Maemo SDKs completely and starting Xephyr and exporing the display from Scratchbox, When I am trying to execute "af-sb-init.sh start" command, it is giving the below error:


[sbox-DIABLO_ARMEL: ~] > af-sb-init.sh start
Note: For remote X connections DISPLAY should contain hostname!
Starting DBUS system bus
Starting D-BUS session bus daemon
Starting Maemo Launcher: maemo-launcher.
defender: died my parent is not who he claims to be
maemo-launcher: warning rising the oom shield for pid=19870 status=2816
Starting Sapwood image server
Starting Matchbox window manager
Starting clipboard-manager
qemu: Unsupported syscall: 307
qemu: Unsupported syscall: 305
mbpixbuf: unable to use XShm. DISPLAY remote?
qemu: Unsupported syscall: 306
qemu: Unsupported syscall: 308
sapwood-server[19883]: GLIB INFO default - server started
Starting Keyboard
maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'
Starting Hildon Desktop
maemo-launcher: invoking '/usr/bin/hildon-desktop.launch'
[sbox-DIABLO_ARMEL: ~] > qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
/home/chandra/.osso/current-gtk-key-theme:1: Unable to find include file: "keybindings.rc"
qemu: Unsupported syscall: 316
hildon-desktop[19940]: GLIB WARNING ** gnome-vfs-modules - Could not initialize inotify
qemu: uncaught target signal 11 (Segmentation fault) - exiting
maemo-launcher: child (pid=19925) terminated due to exit()=245
hildon-desktop[19940]: GLIB WARNING ** default - unable to register TN callback for /usr/share/applications/hildon
/home/chandra/.osso/current-gtk-key-theme:1: Unable to find include file: "keybindings.rc"
qemu: uncaught target signal 4 (Illegal instruction) - exiting
maemo-launcher: child (pid=19940) terminated due to exit()=252

Anybody faced this problem and anybody help me?

Thanks in advance.

Regards
Chandra

I don't use Xephyr. I'm using vncserver to start a vnc server with the required dimensions, and vncviewer to interact with the server. I've never had any problem, running scratchbox configured for OS2007HE on Fedora 9.

Hi,

Thanks for your response. Can you please tell step bystep procedure to work with VNC Server?

Regards
Chandra

run in the fedora xterm:
$ Xvnc :1 -geometry 800x480 -SecurityTypes None &
$ vncviewer :1

This should bring up the window with the Xvnc server.
In scratchbox do
# export DISPLAY=:1.0
# af-sb-init.sh start

You should see in the VNC window the environment. Now that I payed a bit more attention to your problem, it may not be possible to launch the ARMEL version of the environment on x86 hosts - qemu still has it's fair share of problems. The environment works best if you use it in X86 mode, and then switch to armel only to compile binaries for the device
The best result for debugging ARMEL is to setup your device with GDB and a remote filesystem and run the debugging on the device itself. To ease up the screen interaction, install also the vncserver on the device and use it through vncviewer.