[maemo-developers] Xephyr trouble

From: Claudio Scordino cloud.of.andor at gmail.com
Date: Mon Mar 12 12:38:54 EET 2007
Alma Prlja wrote:
> I have some trubles with the scratchbox and maemo. According to Maemo
> tutorial I should use a Xephyr graphical window to run the application.
> When I installed the sctachbox 2 months ago everything was OK but now I
> can not run the maemo applications. When I run the Xephyr with
>> ./start-xephyr.sh
> first the window opens then when we close the window I get this message
> X connection to :0.0 broken (explicit kill or server shutdown).
> if I ignore that message and try to run the maemo from the scratchbox with
> [sbox-SDK_PC: ~] > export DISPLAY=:2
> [sbox-SDK_PC: ~] > af-sb-init.sh start
> I get this
> 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[5269]: GLIB CRITICAL
> ** Gdk - gdk_display_close: assertion `GDK_IS_DISPLAY (display)' failed
> .
> Starting Sapwood image server
> sapwood-server[5284]: GLIB WARNING ** Gdk - cannot open display: (null)
> Starting Matchbox window manager
> matchbox-wm: can't open display! check your DISPLAY variable.
> Starting clipboard-manager
> Starting Keyboard
> Could not open display. Is the DISPLAY environment variable set?
> 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: ~] > maemo-launcher: child (pid=5323) exited due to signal=11
> maemo-launcher: child (pid=5330) exited due to signal=11
> Does anybody know the solution to this problem

I've put

export DISPLAY=

in the .bashrc inside Scratchbox.


Claudio Scordino		
Software Engineer

Evidence Srl
Embedded Real-Time solutions

More information about the maemo-developers mailing list