dbus scratchbox problem - Page 2 - maemo.org

Active Topics

Error after installing Leste on sdcard (17)
to Maemo 7 / Leste by Arno_11 - 13 hrs, 31 mins ago
Maemo 20th Anniversary (4)
to Brainstorm by teroyk - 1 day, 18 hrs ago
Nokia Booklet 3G (RX-75) Drivers (64)
to Alternatives by teroyk - 1 day, 18 hrs ago
Porting apps to Leste (46)
to Maemo 7 / Leste by teroyk - 3 days, 22 hrs ago
more...

Page 2 of 2

< Prev

Thread Tools

	OSEmuTech	2008-02-03 , 02:35
	Posts: 466 \| Thanked: 142 times \| Joined on Jan 2008 @ Temple Terrorist, FL	#11

I'm getting about the same thing (armel/i386) and will be investigating the problem. This is on Ubuntu 7.10 Desktop running on VMware Server 1.04.

Code:


[sbox-CHINOOK_ARMEL: ~] > export DISPLAY=:2
[sbox-CHINOOK_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: error rising the oom shield for pid=10217 status=2816
Starting Sapwood image server
Starting Matchbox window manager
qemu: Unsupported syscall: 307
qemu: Unsupported syscall: 305
mbpixbuf: unable to use XShm. DISPLAY remote?
qemu: Unsupported syscall: 306
qemu: Unsupported syscall: 308
Starting clipboard-manager
sapwood-server[10237]: 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'
[sbox-CHINOOK_ARMEL: ~] > qemu: Unsupported syscall: 264
process 10285: 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=10285) terminated due to exit()=127
process 10286: 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 10286 found in the kindergarten.
maemo-launcher: child (pid=10286) terminated due to exit()=127
/home/osemu/.osso/current-gtk-key-theme:1: Unable to find include file: "keybindings.rc"
process 10271: 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=10271) terminated due to exit()=127
process 10287: 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 10287 found in the kindergarten.
maemo-launcher: child (pid=10287) terminated due to exit()=127