Hi, The last time, my Maemo 4.0 worked well, but this morning, I can't start it anymore. Here's the steps I do: $ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite Open New terminal: $ setarch i386 $ sudo /scratchbox/sbin/sbox_ctl start $ /scratchbox/login [sbox-CHINOOK_ARMEL: ~] > export DISPLAY=:2 [sbox-CHINOOK_ARMEL: ~] > af-sb-init.sh start The output is: ------------------------------------------------------------------------------ Note: For remote X connections DISPLAY should contain hostname! Sample files present. DBUS system bus is already running, doing nothing D-BUS session bus daemon is already running, doing nothing Starting Maemo Launcher: maemo-launcherdefender: died my parent is not who he claims to be maemo-launcher: error rising the oom shield for pid=4859 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[4875]: GLIB INFO default - server started Starting Keyboard maemo-launcher: invoking '/usr/bin/hildon-input-method.launch' qemu: Unsupported syscall: 264 Starting Hildon Desktop maemo-launcher: invoking '/usr/bin/hildon-desktop.launch' qemu: Unsupported syscall: 264 [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 See the manual page for dbus-uuidgen to correct this issue. D-Bus not built with -rdynamic so unable to print a backtrace qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 maemo-launcher: child (pid=4940) terminated due to exit()=127 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 See the manual page for dbus-uuidgen to correct this issue. D-Bus not built with -rdynamic so unable to print a backtrace qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 maemo-launcher: no child 4941 found in the kindergarten. maemo-launcher: child (pid=4941) terminated due to exit()=127 /home/testx64/.osso/current-gtk-key-theme:1: Unable to find include file: " keybindings.rc" 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 See the manual page for dbus-uuidgen to correct this issue. D-Bus not built with -rdynamic so unable to print a backtrace qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 maemo-launcher: child (pid=4925) terminated due to exit()=127 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 See the manual page for dbus-uuidgen to correct this issue. D-Bus not built with -rdynamic so unable to print a backtrace qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 maemo-launcher: no child 4942 found in the kindergarten. maemo-launcher: child (pid=4942) terminated due to exit()=127 -------------------------------------------------------------------------------------------------------- Please take a look and help me to fix this problem. Thanks in advance! Jakov -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.maemo.org/pipermail/maemo-users/attachments/20080215/bffa1911/attachment.htm
