<br><br>Hi, <br>I'm a new comer in this field with maemo.<br><br>Actually, I want to launch Maemo UIs onto several Xephyrs. <br>So I found a thread related to this problem on this mailing list. At that time, author was Sampath. Maybe the subject of that thread is the same as mine. :) In the previous thread, there was just one solution about launching several Xephyrs using a wrapper script(
e.g. start-xephyr.sh). There was not an answer for Maemo UI problems....<br><br>Finally, when I try to launch Maeomo UI(af-sb-init.sh start) on each xephyr, it failed except the first one.<br>The detail situation of is follows..
<br><br> 1) I made 2 start-xephyr.sh, it works for each user. <br> For a user "kevin"<br> #!/bin/sh -e<br> prefix=/scratchbox/users/kevin/targets/SDK_X86/usr<br> export LD_LIBRARY_PATH=${prefix}/lib; export LD_LIBRARY_PATH
<br> exec ${prefix}/bin/Xephyr :$1 -host-cursor -screen 800x480x16 -dpi 96 -ac<br> <br> For a user "dino"<br> #!/bin/sh -e<br> prefix=/scratchbox/users/dino/targets/SDK_X86/usr <br> export LD_LIBRARY_PATH=${prefix}/lib; export LD_LIBRARY_PATH
<br> exec ${prefix}/bin/Xephyr :$1 -host-cursor -screen 800x480x16 -dpi 96 -ac<br><br> <br> 2) Then, I executed these scripts on the gdm xserver(Ubuntu 6.1 Edgy distributed)<br> root$start-xephyr-kevin.sh 2<br> root$start-
xephyr-dino.sh 3<br><br> as a result, on the screen, 2 Xephyr launched.<br><br> 3) On an other PC, executed terminal program(SecureCRT) and then I logged in server as other users, kevin and dino.<br><br> 4) Then I logged in scratchbox(Apophis (Current stable version)) as each user.
<br><br> 5) For the first time, kevin set its DISPLAY, like this<br> [sbox-SDK_X86: ~] > export DISPLAY=<a href="http://127.0.0.1:2">127.0.0.1:2</a><br><br> and then another user, dino did the same work except to number of DISPLAY
<br> <br> [sbox-SDK_X86: ~] > export DISPLAY=<a href="http://127.0.0.1:3">127.0.0.1:3</a><br><br><br> 6) Then, kevin launched Maemo UI firstly<br><br> [sbox-SDK_X86: ~] > af-sb-init.sh start<br><br> ..........as a result, it worked well, I could find that maemo UI launched on the xephyr displayed on 2
<br> <br> 7) Lastly, dino launched Maemo UI, like this<br><br> [sbox-SDK_X86: ~] > af-sb-init.sh start<br><br> ..........as a result, it terminated...with that log.<br><br> /usr/bin/af-sb-init.sh: line 1: export: `bus:': not a valid identifier
<br> /usr/bin/af-sb-init.sh: line 1: export: `/tmp/session_bus_socket:': not a valid identifier<br> Sample files present. <br> Starting DBUS system bus<br> Starting D-BUS session bus daemon<br> /usr/bin/af-
sb-init.sh: line 1: export: `bus:': not a valid identifier<br> /usr/bin/af-sb-init.sh: line 1: export: `/tmp/session_bus_socket:': not a valid identifier <br> /etc/init.d/maemo-launcher: line 1: export: `bus:': not a valid identifier
<br> /etc/init.d/maemo-launcher: line 1: export: `/tmp/session_bus_socket:': not a valid identifier<br> Starting Maemo Launcher: maemo-launcher/home/dino/.osso/current-gtk-key-theme:1: Unable to find include file: "
keybindings.rc" <br> maemo-launcher: died binding to invoker socket<br> start failed.<br> Starting Sapwood image server<br> sapwood-server[12755]: GLIB INFO default - server started <br> Starting Matchbox window manager
<br> matchbox: WARNING: failed to load /usr/share/matchbox/mbnoapp.xpm . Disabling icons. <br> matchbox: failed to load keyboard config<br> Starting clipboard-manager<br> Starting Keyboard<br> Starting MAEMO AF Desktop
<br> [sbox-SDK_X86: ~] ><br><br> 8) Following End.<br><br><br> Well, I think it might be problem at DBUS sessions and maemo UI initscript...<br> I expected that it'd work well if that problems are fixed...<br> Somebody who knows that issue, please, let me know how to fix it...
<br><br> Thanks,<br> BRs.<br><br> Kevin, K Park.<br><br> <br><br> <br>