Hi Levi,<br><br>Thanks for the reply.<br>Please see below for my response.<br><br>Thanks and Regards,<br>Sampath<br><br><div><span class="gmail_quote">On 1/31/07, <b class="gmail_sendername">Levi Bard</b> <<a href="mailto:taktaktaktaktaktaktaktaktaktak@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
taktaktaktaktaktaktaktaktaktak@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> 1:<br>> ---<br>> I tried to launch the Xephyr using "# ./start-
xephyr.sh &" command. I am<br>> able to launch for the first login. Keeping this Xephyr active, When I try<br>> to launch it from a different login from a different PC I am getting the<br>> below error:
<br>
><br>> "<br>> Fatal server error:<br>> Server is already active for display 2<br>> If this server is no longer running, remove /tmp/.X2-lock<br>> and start again.<br>> "<br>
> If I close the first instance of xephyr and try again, I am able to launch
<br>> it from the second login.<br>><br>> Is there any way to launch xephyr from different clients at same time?<br><br>I would suggest creating another xephyr script that launches xephyr on<br>a different display ( exec ${prefix}/bin/Xephyr :3 -host-cursor
<br>-screen 800x480x16 0dpi 96 -ac ), or alternatively write a script that<br>takes the display as a parameter.</blockquote><div><br>Sampath: This works and I am able to launch Xephyr parallely from different logins in different PCs.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> 2:<br>> ---<br>> I tried to launch the Xephyr using "# ./start-
xephyr.sh &" command. I am<br>> able to launch for the first login. Then I tried to start the Maemo UI in<br>> the Xephyr window using the command "[sbox-SDK_PC: ~] > af-sb-init.sh<br>> start". The Maemo window started without any problems.
<br>> I stopped the Maemo UI "[sbox-SDK_PC: ~] > af-sb-init.sh stop" and closed<br>> the Xephyr window.<br>> From a different client I launched Xephyr and tried to start the Maemo UI<br>> using the command "[sbox-SDK_PC: ~] >
af-sb-init.sh start". Maemo Ui is not<br>> started and I am getting the below messages:<br><br>After starting xephyr, did you set DISPLAY to :2 in your shell?</blockquote><div><br>Sampath:<br>Yes, I did set the DISPLAY to :2.
<br>Even with the solution to first problem, this problem still exists. I am getting the same errors. That is...<br><br>When I try to start Maemo UI from the second login, I am getting the below shown messages:<br>"
<br>[sbox-SDK_PCSAM: ~] > af-sb-init.sh start<br>Note: For remote X connections DISPLAY should contain hostname!
<br>Sample files present.<br>Starting DBUS system bus<br>Starting D-BUS session bus daemon<br>Starting Maemo Launcher: maemo-launchermaemo-launcher: died binding to invoker socket<br> start failed.<br>Starting Sapwood image server
<br>Starting Matchbox window manager<br>sapwood-server[9332]: GLIB INFO default - server started<br>Starting clipboard-manager<br>Starting Keyboard<br>Starting MAEMO AF Desktop<br>"<br><br>After that I am not even able to launch Maemo UI on first login also (which was working initially).
<br>I am getting below messages in the first login when I try to launch Maemo UI:<br><br>"<br>[sbox-SDK_PC: ~] > af-sb-init.sh start<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>Note: For remote X connections DISPLAY should contain hostname!<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.<br>Starting Sapwood image server<br>Starting Matchbox window manager<br>Starting clipboard-manager
<br>Starting Keyboard<br>maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'<br>Starting MAEMO AF Desktop<br>maemo-launcher: invoking '/usr/bin/maemo_af_desktop.launch'<br>[sbox-SDK_PC: ~] > sapwood-server[12935]: GLIB INFO default - server started
<br>hildon-input-method[12959]: GLIB WARNING ** default - Could not initialize osso from hildon-input-method<br>maemo-launcher: child (pid=12974) exited due to exit()=1<br>hildon-input-method[12959]: GLIB WARNING ** default - Could not register the osso_hw_set_event_cb
<br>hildon-input-method[12959]: GLIB MESSAGE default - keyboard up and running<br>"<br><br>I have to restart the server to make things work for the first login.<br><br>Please, let me know if there is any solution.<br>
<br>Thanks and regards,<br>Sampath<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
--<br>Just stop and take your secret journey, you will be a new box. --Leeta<br><a href="http://www.gnu.org/philosophy/shouldbefree.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.gnu.org/philosophy/shouldbefree.html
</a><br></blockquote></div><br>