[maemo-developers] Xephyr crash with segmentation fault

From: David Hautbois david.hautbois at free.fr
Date: Thu Jun 14 20:37:26 EEST 2007
Hi
I use maemo 3.0 SDK on debian etch(i386).
Today, Xephyr crashes with segmentation fault :

Xephyr :
david at saturne:~$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac
Extended Input Devices not yet supported. Impelement it at line 625 in 
../../../../hw/kdrive/src/kinput.c
Could not init font path element /usr/share/fonts/X11/cyrillic, removing 
from list!
Could not init font path element 
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!
Segmentation fault

Scratchbox:
david at saturne:~$ /scratchbox/login

Welcome to Scratchbox, the cross-compilation toolkit!

Use 'sb-menu' to change your compilation target.
See /scratchbox/doc/ for documentation.

[sbox-SDK_X86: ~] > export DISPLAY=:2
[sbox-SDK_X86: ~] > af-sb-init.sh start
AF Warning: '/etc/osso-af-init/keyboard.defs' not found
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-launcher/home/david/.osso/current-gtk-key-theme:1: Unable to find 
include file: "keybindings.rc"
maemo-launcher: error rising the oom shield for pid=4164 status=5632
.
Starting Sapwood image server
Starting Matchbox window manager
Starting clipboard-manager
Starting MAEMO AF Desktop
maemo-launcher: invoking '/usr/bin/maemo_af_desktop.launch'
[sbox-SDK_X86: ~] > sapwood-server[4175]: GLIB WARNING ** Gdk - cannot 
open display: (null)
matchbox-wm: can't open display! check your DISPLAY variable.
Could not open display. Is the DISPLAY environment variable set?
maemo_af_desktop[4210]: GLIB CRITICAL ** GLib-GObject - 
g_object_set_data: assertion `G_IS_OBJECT (object)' failed
maemo-launcher: child (pid=4210) terminated due to signal=11
maemo-launcher: no child 4215 found in the kindergarten.
maemo-launcher: child (pid=4215) terminated due to exit()=0

I didn't update Scratch as recommended in a previous post.
Can it be the problem ?

Thanks.

David.


More information about the maemo-developers mailing list