[maemo-developers] [maemo-developers] Re: Maemo kit development and remote access
From: donars guillaume gdonars at gmail.comDate: Wed Apr 12 11:23:28 EEST 2006
- Previous message: [maemo-developers] Maemo kit development and remote access
- Next message: [maemo-developers] Plugged in USB, not booting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi again,
I will try to be more precise, last time I wasn't at work.
So when I run: af-sb-init.sh start in my ssh client, I see in the xephyr
window the environnement trying to run but it disappeared immediatly.
And I have this error message:
---------------------------------------------------------------------------------------------------------------------------------------------
x-SDK_PC: ~] > af-sb-init.sh start
Sample files present.
Starting Maemo Launcher: maemo-launcher start failed.
Starting DBUS system bus
Starting D-BUS session bus daemon
Sapwood image server is already running, doing nothing
Starting Matchbox window manager
Keyboard is already running, doing nothing
root window unavailible (maybe another wm is running?)
Starting MAEMO AF Desktop
[sbox-SDK_PC: ~] > maemo_af_desktop[16427]: GLIB CRITICAL ** GLib-GObject -
g_object_set: assertion `G_IS_OBJECT (object)' failed
maemo_af_desktop[16427]: osso_state_close:282: Unable to close state file:
Bad file descriptor
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
TRACE LOG: status_bar_main: 4 add prespecified items
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin sound:
/usr/lib/hildon-status-bar/libsound.so: cannot open shared object file: No
such file or directory
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin sound
maemo_af_desktop[16427]: Item not properly loaded.
This function is only called, if a item couldn't initialise itself
properly.
See hildon_status_bar_item_init/new for more information
maemo_af_desktop[16427]: Statusbar item add failed for sound
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin
internet: /usr/lib/hildon-status-bar/libinternet.so: cannot open shared
object file: No such file or directory
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin
internet
maemo_af_desktop[16427]: Item not properly loaded.
This function is only called, if a item couldn't initialise itself
properly.
See hildon_status_bar_item_init/new for more information
maemo_af_desktop[16427]: Statusbar item add failed for internet
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin
gateway: /usr/lib/hildon-status-bar/libgateway.so: cannot open shared object
file: No such file or directory
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin
gateway
maemo_af_desktop[16427]: Item not properly loaded.
This function is only called, if a item couldn't initialise
itself properly.
See hildon_status_bar_item_init/new for more information
maemo_af_desktop[16427]: Statusbar item add failed for gateway
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin
battery: /usr/lib/hildon-status-bar/libbattery.so: cannot open shared object
file: No such file or directory
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin
battery
maemo_af_desktop[16427]: Item not properly loaded.
This function is only called, if a item couldn't initialise
itself properly.
See hildon_status_bar_item_init/new for more information
maemo_af_desktop[16427]: Statusbar item add failed for battery
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin
display: /usr/lib/hildon-status-bar/libdisplay.so: cannot open shared object
file: No such file or directory
maemo_af_desktop[16427]: HildonStatusBarItem: Unable to open plugin
display
maemo_af_desktop[16427]: Item not properly loaded.
This function is only called, if a item couldn't initialise
itself properly.
See hildon_status_bar_item_init/new for more information
maemo_af_desktop[16427]: Statusbar item add failed for display
TRACE LOG: status_bar_main: 5 add user items
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
sapwood-server[16289]: GLIB WARNING ** Gdk - The gdk_draw_*_image
require the drawable argument to
have a specified colormap. All windows have a colormap,
however, pixmaps only have colormap by default if they
were created with a non-NULL window argument. Otherwise
a colormap must be set on them with gdk_drawable_set_colormap
maemo_af_desktop[16427]: GLIB WARNING ** default -
qgn_plat_task_navigation_button_03_normal.png: pixmap[1][1]:
gdk_pixmap_foreign_new(800003) failed
maemo_af_desktop[16427]: GLIB WARNING ** default - Aieeee
maemo_af_desktop[16427]: GLIB WARNING ** default -
qgn_plat_task_navigation_button_03_normal.png: pixmask[1][1]: no pixmap
sapwood-server[16289]: GLIB WARNING ** Gdk - The gdk_draw_*_image
require the drawable argument to
have a specified colormap. All windows have a colormap,
however, pixmaps only have colormap by default if they
were created with a non-NULL window argument. Otherwise
a colormap must be set on them with gdk_drawable_set_colormap
The program 'sapwood-server' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue'.
(Details: serial 80 error_code 2 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported
asynchronously;
that is, you will receive the error a while after causing
it.
To debug your program, run it with the --sync command
line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the
gdk_x_error() function.)
maemo_af_desktop[16427]: GLIB ERROR ** default - sapwood-theme:
Failed to load pixmap file
/usr/share/themes/default/gtk-2.0/../images/qgn_plat_task_navigation_skin_01.png:
read 0, expected 80 bytes
aborting...
[sbox-SDK_PC: ~] >
----------------------------------------------------------------------------------------------------------------------------------------
With vnc, the xephyr windows closed and I have a "segmentation fault" error,
in windows and in linux.
Thank for your help.
guymage.
On 4/10/06, donars guillaume <gdonars at gmail.com> wrote:
>
> Hi,
>
> I have to configure a remote access to maemo development kit. Most of
> connections will be from a windows XP and I try to use vnc or an ssh-client
> + exceed but I have the same problem.
> I have followed the tutorial and when I run " af-sb-init.sh start", the
> xephyr windows brutally close and i get the "segmentation fault" message in
> the terminal i use for it. In the terminal where I have down the af-sb..
> command I got this message or something near like that:
>
> "launch maemo .. , maemo .. failed to start"
> and others errors after because the xephyr windows is closed.
>
> I precise that it works in local.
>
> If someone have an idea, thank you for advance.
>
> Best regards.
>
>
> Guymage.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20060412/5d705b30/attachment.htm
- Previous message: [maemo-developers] Maemo kit development and remote access
- Next message: [maemo-developers] Plugged in USB, not booting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]