Hi,<br><br>The last time, my Maemo 4.0 worked well, but this morning, I can't start it anymore. Here's the steps I do:<br><br>$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite <br><br>Open New terminal:<br>
$ setarch i386<br>$ sudo /scratchbox/sbin/sbox_ctl start<br>$ /scratchbox/login<br><br>[sbox-CHINOOK_ARMEL: ~] > export DISPLAY=:2<br>[sbox-CHINOOK_ARMEL: ~] > af-sb-init.sh start<br><br>The output is: ------------------------------------------------------------------------------<br>
<br>Note: For remote X connections DISPLAY should contain hostname!<br>Sample files present.<br>DBUS system bus is already running, doing nothing<br>D-BUS session bus daemon is already running, doing nothing<br>Starting Maemo Launcher: maemo-launcherdefender: died my parent is not who he claims to be<br>
maemo-launcher: error rising the oom shield for pid=4859 status=2816<br>.<br>Starting Sapwood image server<br>Starting Matchbox window manager<br>Starting clipboard-manager<br>qemu: Unsupported syscall: 307<br>qemu: Unsupported syscall: 305<br>
mbpixbuf: unable to use XShm. DISPLAY remote?<br>qemu: Unsupported syscall: 306<br>qemu: Unsupported syscall: 308<br>sapwood-server[4875]: GLIB INFO default - server started<br>Starting Keyboard<br>maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'<br>
qemu: Unsupported syscall: 264<br>Starting Hildon Desktop<br>maemo-launcher: invoking '/usr/bin/hildon-desktop.launch'<br>qemu: Unsupported syscall: 264<br>[sbox-CHINOOK_ARMEL: ~] > process 4940: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory<br>
See the manual page for dbus-uuidgen to correct this issue.<br> D-Bus not built with -rdynamic so unable to print a backtrace<br>qemu: Unsupported syscall: 268<br>qemu: Unsupported syscall: 238<br>qemu: Unsupported syscall: 268<br>
qemu: Unsupported syscall: 238<br>maemo-launcher: child (pid=4940) terminated due to exit()=127<br>process 4941: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory<br>
See the manual page for dbus-uuidgen to correct this issue.<br> D-Bus not built with -rdynamic so unable to print a backtrace<br>qemu: Unsupported syscall: 268<br>qemu: Unsupported syscall: 238<br>qemu: Unsupported syscall: 268<br>
qemu: Unsupported syscall: 238<br>maemo-launcher: no child 4941 found in the kindergarten.<br>maemo-launcher: child (pid=4941) terminated due to exit()=127<br>/home/testx64/.osso/current-gtk-key-theme:1: Unable to find include file: "keybindings.rc"<br>
process 4925: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory<br>See the manual page for dbus-uuidgen to correct this issue.<br>
D-Bus not built with -rdynamic so unable to print a backtrace<br>qemu: Unsupported syscall: 268<br>qemu: Unsupported syscall: 238<br>qemu: Unsupported syscall: 268<br>qemu: Unsupported syscall: 238<br>maemo-launcher: child (pid=4925) terminated due to exit()=127<br>
process 4942: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory<br>See the manual page for dbus-uuidgen to correct this issue.<br>
D-Bus not built with -rdynamic so unable to print a backtrace<br>qemu: Unsupported syscall: 268<br>qemu: Unsupported syscall: 238<br>qemu: Unsupported syscall: 268<br>qemu: Unsupported syscall: 238<br>maemo-launcher: no child 4942 found in the kindergarten.<br>
maemo-launcher: child (pid=4942) terminated due to exit()=127<br><br>--------------------------------------------------------------------------------------------------------<br><br>Please take a look and help me to fix this problem.<br>
<br>Thanks in advance!<br><br>Jakov<br>