Starting up runtime for fremantle5.0minimal_armel...
Forcing bit depth to be 24.
Sample files present.
Starting DBUS system bus
Starting D-BUS session bus daemon
Starting Maemo Launcher: maemo-launcher.
maemo-launcher: warning raising the oom shield for pid=1765 status=5632
getsockopt level=1 optname=17 not yet supported
Starting Sapwood image server
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
Error setting value: Configuration server couldn't be contacted: D-BUS error: Unable to store a value at key '/apps/osso/inputmethod/have-internal-keyboard', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Error setting value: Configuration server couldn't be contacted: D-BUS error: Unable to store a value at key '/system/osso/af/slide-open', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Starting hildon-desktop
maemo-launcher: invoking '/usr/bin/hildon-desktop.launch'
maemo-launcher: invoking '/usr/bin/hildon-status-menu.launch'
maemo-launcher: invoking '/usr/bin/hildon-home.launch'
Configuring Hildon Input Method
maemo-launcher: opening of /usr/bin/hildon-desktop.launch took 26700 usec
maemo-launcher: opening of /usr/bin/hildon-status-menu.launch took 13613 usec
sudo: must be setuid root
maemo-launcher: opening of /usr/bin/hildon-home.launch took 11025 usec
Starting Keyboard
Initializing trackerd...
qemu: Unsupported syscall: 314
qemu: Unsupported syscall: 314
Starting browser daemon: browserd
Messages from sb2:
2010-07-25 13:42:01.947 (WARNING)	maemo-launcher[1766/140564822185728]	SUID bit set for '/home/mase/.maemo-sdk/rootstraps/armel/fremantle5.0minimal_armel/usr/lib/maemo-launcher/defender' (SB2 may be disabled)
2010-07-25 13:42:02.557 (WARNING)	bash[1796/140266862835456]	SUID bit set for '/home/mase/.maemo-sdk/rootstraps/armel/fremantle5.0minimal_armel/usr/bin/sudo' (SB2 may be disabled)
# exit 0 (0)
Done

mase@mase1:~$ getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
maemo-launcher: child (pid=1795) terminated due to signal=11
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
GConf Error: Configuration server couldn't be contacted: D-BUS error: Unable to store a value at key '/apps/osso/inputmethod/available_languages', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported