[maemo-developers] [maemo-developers] Can we launch Xephyr from different clients connected to a server

From: Sampath Goud sampath.baddam at gmail.com
Date: Thu Feb 1 07:02:18 EET 2007
Hi Levi,

Thanks for the reply.
Please see below for my response.

Thanks and Regards,
Sampath

On 1/31/07, Levi Bard < taktaktaktaktaktaktaktaktaktak at gmail.com> wrote:
>
> > 1:
> >  ---
> >  I tried to launch the Xephyr using "# ./start- xephyr.sh &" command. I
> am
> > able to launch for the first login. Keeping this Xephyr active, When I
> try
> > to launch it from a different login from a different PC I am getting the
> > below error:
> >
> > "
> > Fatal server error:
> > Server is already active for display 2
> >         If this server is no longer running, remove /tmp/.X2-lock
> >         and start again.
> > "
> > If I close the first instance of xephyr and try again, I am able to
> launch
> > it from the second login.
> >
> > Is there any way to launch xephyr from different clients at same time?
>
> I would suggest creating another xephyr script that launches xephyr on
> a different display ( exec ${prefix}/bin/Xephyr :3 -host-cursor
> -screen 800x480x16 0dpi 96 -ac ), or alternatively write a script that
> takes the display as a parameter.


Sampath: This works and  I am able to launch Xephyr parallely from different
logins in different PCs.

> 2:
> > ---
> > I tried to launch the Xephyr using "# ./start- xephyr.sh &" command. I
> am
> > able to launch for the first login. Then I tried to start the Maemo UI
> in
> > the Xephyr window using the command "[sbox-SDK_PC: ~] > af-sb-init.sh
> > start". The Maemo window started without any problems.
> > I stopped the Maemo UI "[sbox-SDK_PC: ~] > af-sb-init.sh stop" and
> closed
> > the Xephyr window.
> > From a different client I launched Xephyr and tried to start the Maemo
> UI
> > using the command "[sbox-SDK_PC: ~] > af-sb-init.sh start". Maemo Ui is
> not
> > started and I am getting the below messages:
>
> After starting xephyr, did you set DISPLAY to :2 in your shell?


Sampath:
Yes, I did set the DISPLAY to :2.
Even with the solution to first problem, this problem still exists. I am
getting the same errors. That is...

When I try to start Maemo UI from the second login, I am getting the below
shown messages:
"
[sbox-SDK_PCSAM: ~] > af-sb-init.sh start
Note: For remote X connections DISPLAY should contain hostname!
Sample files present.
Starting DBUS system bus
Starting D-BUS session bus daemon
Starting Maemo Launcher: maemo-launchermaemo-launcher: died binding to
invoker socket
 start failed.
Starting Sapwood image server
Starting Matchbox window manager
sapwood-server[9332]: GLIB INFO default - server started
Starting clipboard-manager
Starting Keyboard
Starting MAEMO AF Desktop
"

After that I am not even able to launch Maemo UI on first login also (which
was working initially).
I am getting below messages in the first login when I try to launch Maemo
UI:

"
[sbox-SDK_PC: ~] > af-sb-init.sh start
/usr/bin/af-sb-init.sh: line 1: export: `bus:': not a valid identifier
/usr/bin/af-sb-init.sh: line 1: export: `/tmp/session_bus_socket:': not a
valid identifier
Note: For remote X connections DISPLAY should contain hostname!
Sample files present.
Starting DBUS system bus
Starting D-BUS session bus daemon
/usr/bin/af-sb-init.sh: line 1: export: `bus:': not a valid identifier
/usr/bin/af-sb-init.sh: line 1: export: `/tmp/session_bus_socket:': not a
valid identifier
/etc/init.d/maemo-launcher: line 1: export: `bus:': not a valid identifier
/etc/init.d/maemo-launcher: line 1: export: `/tmp/session_bus_socket:': not
a valid identifier
Starting Maemo Launcher: maemo-launcher.
Starting Sapwood image server
Starting Matchbox window manager
Starting clipboard-manager
Starting Keyboard
maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'
Starting MAEMO AF Desktop
maemo-launcher: invoking '/usr/bin/maemo_af_desktop.launch'
[sbox-SDK_PC: ~] > sapwood-server[12935]: GLIB INFO default - server started
hildon-input-method[12959]: GLIB WARNING ** default - Could not initialize
osso from hildon-input-method
maemo-launcher: child (pid=12974) exited due to exit()=1
hildon-input-method[12959]: GLIB WARNING ** default - Could not register the
osso_hw_set_event_cb
hildon-input-method[12959]: GLIB MESSAGE default - keyboard up and running
"

I have to restart the server to make things work for the first login.

Please, let me know if there is any solution.

Thanks and regards,
Sampath


--
> Just stop and take your secret journey, you will be a new box. --Leeta
> http://www.gnu.org/philosophy/shouldbefree.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20070201/c8bf9bc3/attachment.htm 
More information about the maemo-developers mailing list