[maemo-developers] Xephyr crash with segmentation fault
From: Daniel Martín Yerga dyerga at gmail.comDate: Sun Jun 17 17:08:49 EEST 2007
- Previous message: Xephyr crash with segmentation fault
- Next message: Xephyr crash with segmentation fault
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 17/06/07, David Hautbois <david.hautbois at free.fr> wrote: > Hi > I have more details about my problems : > > 1 - I launch Xpehyr : > Command : > Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac > > Result : > 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! > > 2 - I launch scratchbox : > Command : > /scratchbox/login > Result : > Welcome to Scratchbox, the cross-compilation toolkit! > > Use 'sb-menu' to change your compilation target. > See /scratchbox/doc/ for documentation. > > 3 - I launch the hildon environnement : > Command : > export DISPLAY=:2 > af-sb-init.sh start > Result : > 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" > . > Starting Sapwood image server > maemo-launcher: error rising the oom shield for pid=3716 status=5632 > 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[3727]: GLIB WARNING ** Gdk - > cannot open display: (null) > matchbox-wm: can't open display! check your DISPLAY variable. > maemo_af_desktop[3762]: GLIB CRITICAL ** GLib-GObject - > g_object_set_data: assertion `G_IS_OBJECT (object)' failed > Could not open display. Is the DISPLAY environment variable set? > maemo-launcher: child (pid=3762) terminated due to signal=11 > maemo-launcher: no child 3767 found in the kindergarten. > maemo-launcher: child (pid=3767) terminated due to exit()=0 > > And Xephyr crashes : > Segmentation fault > > 4 - I launch Xephyr one more time : > Command : > Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac > Result : > 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! > > 5 - I launch the hildon environnement one more time : > Command : > af-sb-init.sh start > Result : > AF Warning: '/etc/osso-af-init/keyboard.defs' not found > Note: For remote X connections DISPLAY should contain hostname! > Sample files present. > DBUS system bus is already running, doing nothing > D-BUS session bus daemon is already running, doing nothing > Starting Maemo Launcher: maemo-launcher start failed. > Starting Sapwood image server > sapwood-server[3941]: GLIB INFO default - server started > Starting Matchbox window manager > matchbox: WARNING: failed to load /usr/share/matchbox/mbnoapp.xpm . > Disabling icons. > Starting clipboard-manager > matchbox: failed to load keyboard config > Starting MAEMO AF Desktop > maemo-launcher: invoking '/usr/bin/maemo_af_desktop.launch' > [sbox-SDK_X86: ~] > maemo-launcher: error kernel w/o support for > user processes rising the oom value > /home/david/.osso/current-gtk-key-theme:1: Unable to find include > file: "keybindings.rc" > maemo_af_desktop[3983]: GLIB WARNING ** default - Could not add > dnotify watch on /usr/share/applications/hildon-home > maemo_af_desktop[3983]: GLIB WARNING ** default - Error when > opening plugin registry: Error opening directory > '/usr/share/applications/hildon-home': No such file or directory > maemo_af_desktop[3983]: GLIB WARNING ** default - Failed to lookup > 'TitleTextColor' color! > maemo_af_desktop[3983]: GLIB WARNING ** default - Unable to read > configuration file at `/home/david/.osso/hildon-home/hildon-home.conf': > No such file or directory > maemo_af_desktop[3983]: GLIB DEBUG default - Background loaded from > cache > maemo_af_desktop[3983]: GLIB DEBUG default - > hildon-home-window.c:510: load complete > maemo_af_desktop[3983]: GLIB DEBUG default - > background-manager.c:1772: applying background > maemo_af_desktop[3983]: GLIB DEBUG default - HildonHome is lowmem: 0 > Showing window > Window shown: 1 > DEBUG position: dummy0 0 > DEBUG position: dummy0 0 > DEBUG position: dummy1 1 > maemo_af_desktop[3983]: GLIB DEBUG default - I couldn't get contents > maemo_af_desktop[3983]: GLIB DEBUG default - Failed to load plugin > bookmark (libtn_bookmark_plugin.so.0.0.0) > maemo_af_desktop[3983]: GLIB DEBUG default - Failed to load plugin > Contact Plugin (libosso-contact-plugin.so) > TRACE LOG: status_bar_main: 1 g_new0 > TRACE LOG: status_bar_main: 2 check panel ptr > TRACE LOG: status_bar_main: 3: init dock > maemo_af_desktop[3983]: GLIB WARNING ** default - Could not load > statusbar extension icon: Icon 'qgn_stat_more' not present in theme > TRACE LOG: status_bar_main: 4 add configured items > TRACE LOG: status_bar_main: 5 add notify for conditional items update > TRACE LOG: status_bar_main: 6 gtk widget show all > TRACE LOG: status_bar_main: 7 if rpc... > TRACE LOG: status_bar_main: 8, status bar initialized successfully > maemo_af_desktop[3983]: GLIB DEBUG default - cannot opent keyfile > maemo_af_desktop[3983]: GLIB DEBUG default - cannot opent keyfile > maemo_af_desktop[3983]: GLIB DEBUG default - cannot opent keyfile > maemo_af_desktop[3983]: GLIB DEBUG default - cannot opent keyfile > maemo_af_desktop[3983]: GLIB DEBUG default - cannot opent keyfile > maemo_af_desktop[3983]: GLIB DEBUG default - Creating menu > > Ok, Hidon environnement is up ! > > I launch a hidonized python/GTK application > Command : > run-standalone.sh ./erminig > > Now it is ok, but sometimes, I don't have the hildon themes : > The wigdets, in my python application, does not appear and I have > recurrent error messages about the sapwood server : > `/usr/lib/sapwood/sapwood-server' MUST be started before applications > python2.5[4514]: GLIB WARNING ** sapwood - sapwood-theme: Failed to > load pixmap file > /usr/share/themes/default/gtk-2.0/../images/qgn_plat_view_button_nesw.png: > Failed to connect to sapwood server using `/var/tmp/sapwood-:2.0': > Connection refused > > So, I need to reboot my PC. > > I think I have this error when I execute the #5 too quickly. > > I had the same problem last week with SDK3.0. > Yesterday, I installed SDK3.1 (in a new scratbox directory), but I have > problems too. > I use Debian Lenny. > > I hope to be understandable.... > > David. > I was having similar problems using the Xephyr version in unstable and testing. Doing a downgrade to the Stable version, it works perfectly, well it doesn't crash. Now I don't remember the exact version numbers. This is a temporary solution, since it should be able to use the new Xephyr version perfectly. Best Regards.
- Previous message: Xephyr crash with segmentation fault
- Next message: Xephyr crash with segmentation fault
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]