[maemo-developers] Xephyr Maemo VMware
From: andrew gatt a.gatt at btinternet.comDate: Mon Jun 25 17:16:37 EEST 2007
- Previous message: watchDog
- Next message: Xephyr Maemo VMware
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I've been trying out the VMware image, although i guess this question
could relate to any installation. I'm trying to get both 2.2 and 3.1 on
the same scratchbox to work properly. The rootstrap seems to have
installed fine and i can log in and compile programs in the 2.2 SDK,
however the xephyr that is started automatically in the VMware image
doesn't seem to support the 2.2 framework - the desktop doesn't render
properly and the menu system doesn't work. I realise now that each SDK
comes with its own Xephyr so I'm trying to start xephyr from the 2.2 SDK
using:
#!/bin/sh
prefix=/scratchbox/users/maemo/targets/SDK2.2_PC/usr
export LD_LIBRARY_PATH=${prefix}/lib; export LD_LIBRARY_PATH
exec ${prefix}/bin/Xephyr :2 -host-cursor -screem 800x480z16 -dpi 96 -ac
which seems to start up Xephyr, however the usual grey background is
white (before af-sb-init..sh start) and when i try af-sb-init.sh it
fails with:
....
Starting Keyboard
maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'
maemo-launcher: child (pid=6199) terminated due to signal=11
/usr/bin/af-sb-init.sh: line 1: 6198 Segmentation fault (core dumped)
$CMD $PARAMS
Starting MAEMO AF Desktop
maemo-launcher: invoking '/usr/bin/maemo_af_desktop.launch'
maemo-launcher: child (pid=6216) terminated due to signal=11
/usr/bin/scratchbox-launcher.sh: line 114: 6215 Segmentation fault
(core dumped) $CMD $PARAMS
Am i not supposed to use the 2.2 SDK Xephyr in which case can someone
tell me how to get the Xephyr bundled with the VMWare image to work with
2.2. Or can someone explain what i'm doing wrong when invoking the 2.2
SDK Xephyr.
Thanks
Andrew
- Previous message: watchDog
- Next message: Xephyr Maemo VMware
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
