Reply
Thread Tools
Posts: 2 | Thanked: 0 times | Joined on Oct 2009 @ London
#1
Hi guys,
I am trying to set up the Maemo SDK following the instructions as per the maemo diablo reference manual. I am attempting to start the application framework (section 3.4.6) and am getting the following output from my sbox:

Code:
[sbox-DIABLO_ARMEL: ~/maemo/stephen-gtk-hello] > af-sb-init.sh start
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.
Sapwood image server is already running, doing nothing
Matchbox window manager is already running, doing nothing
clipboard-manager is already running, doing nothing
Starting Keyboard
maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'
qemu: Unsupported syscall: 264
Starting Hildon Desktop
maemo-launcher: invoking '/usr/bin/hildon-desktop.launch'
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 316
hildon-desktop[5899]: GLIB WARNING ** gnome-vfs-modules - Could not initialize inotify
/home/christina/.osso/current-gtk-key-theme:1: Unable to find include file: "keybindings.rc"
[sbox-DIABLO_ARMEL: ~/maemo/stephen-gtk-hello] > qemu: uncaught target signal 11 (Segmentation fault) - exiting
maemo-launcher: child (pid=5884) terminated due to exit()=245
hildon-desktop[5899]: GLIB WARNING ** default - unable to register TN callback for /usr/share/applications/hildon
/home/christina/.osso/current-gtk-key-theme:1: Unable to find include file: "keybindings.rc"
hildon-desktop[5899]: GLIB WARNING ** default - Error loading plugin: /usr/lib/libbookmarkengine.so.0: symbol __cxa_finalize, version GLIBC_2.4 not defined in file libc.so.6 with link time reference
hildon-desktop[5899]: GLIB WARNING ** default - Error loading plugin: /usr/lib/libbookmarkengine.so.0: symbol __cxa_finalize, version GLIBC_2.4 not defined in file libc.so.6 with link time reference
hildon-desktop[5899]: GLIB WARNING ** default - /usr/lib/libtelepathy-glib.so.0: symbol stdout, version GLIBC_2.4 not defined in file libc.so.6 with link time reference
hildon-desktop[5899]: GLIB WARNING ** default - Error loading module at /usr/lib/hildon-desktop/libosso-contact-plugin.so
qemu: uncaught target signal 11 (Segmentation fault) - exiting
maemo-launcher: child (pid=5899) terminated due to exit()=245
And in my standard shell running this command for Xephyr:

Code:
$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite
And then when I start the application manager I get:

Code:
$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.75" is not allowed to own the service "org.x.config.display2" due to security policies in the configuration file)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
My environment is Ubuntu 9.10. Please let me know anymore environmental information that would help diagnose the problem.

Thanks,
Stephen
 
allnameswereout's Avatar
Posts: 3,397 | Thanked: 1,212 times | Joined on Jul 2008 @ Netherlands
#2
x86-32? Can you try it with x86 instead of armel? You are aware Diablo is not supported anymore, and that you're running an unsupported SDK version?
__________________
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!
 

The Following User Says Thank You to allnameswereout For This Useful Post:
Posts: 452 | Thanked: 522 times | Joined on Nov 2007
#3
I put the answer in this faq a while back; http://wiki.maemo.org/Q%26A_-_SDK_and_Scratchbox

It has the solution to your security issue (which is causing your whole issue I believe). The solution should work on 9.10; I used in on 9.03.
(9.10 & 9.03 are Ubuntu versions)


Nathan

Last edited by Nathan; 2009-10-13 at 16:14. Reason: Ubuntu Version Clarification
 

The Following User Says Thank You to Nathan For This Useful Post:
Posts: 432 | Thanked: 645 times | Joined on Mar 2009
#4
A general command, which is also mentioned in the Q&A:

The ARMEL target should not be used for application testing or running the framework and just for cross compiling. The target is not meant to support this. Please use for any other use than cross-compiling the X86 target.


Cheers Daniel
 

The Following User Says Thank You to danielwilms For This Useful Post:
Posts: 2 | Thanked: 0 times | Joined on Oct 2009 @ London
#5
Originally Posted by allnameswereout View Post
x86-32? Can you try it with x86 instead of armel? You are aware Diablo is not supported anymore, and that you're running an unsupported SDK version?
Changing the target to x86 makes it work alright. I wasn't aware that Diablo was unsupported, I will upgrade now, thanks!

Originally Posted by danielwilms View Post
A general command, which is also mentioned in the Q&A:

The ARMEL target should not be used for application testing or running the framework and just for cross compiling. The target is not meant to support this. Please use for any other use than cross-compiling the X86 target.


Cheers Daniel
Thanks Daniel. Like I said above, x86 works fine for me now. Can you run the ARM targets within QEMU?
 
allnameswereout's Avatar
Posts: 3,397 | Thanked: 1,212 times | Joined on Jul 2008 @ Netherlands
#6
Stephen, ARMEL is only meant for cross compiling. It may or may not work in QEMU guest emulation (which is used when using ARMEL target).

Nathan, what do you mean with version 9.03 and version 9.10?
__________________
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!
 
Posts: 432 | Thanked: 645 times | Joined on Mar 2009
#7
Originally Posted by stephenr View Post
Changing the target to x86 makes it work alright. I wasn't aware that Diablo was unsupported, I will upgrade now, thanks!
It depends on the device you want to develop for. If you have a N8XX you have to use the Diablo SDK to compile for it. For the N900 please use the latest SDK.

Originally Posted by stephenr View Post
Thanks Daniel. Like I said above, x86 works fine for me now. Can you run the ARM targets within QEMU?
No. ARM targets are there just for cross-compiling.

Cheers Daniel
 
Posts: 452 | Thanked: 522 times | Joined on Nov 2007
#8
Originally Posted by allnameswereout View Post
Nathan, what do you mean with version 9.03 and version 9.10?
He mentioned specifically he was using Ubuntu 9.10 (Karmic), 9.03 (Jaunty) which is what I've used. So I was saying that his error is the same as what I got and what I put in the faq is how to fix it on 9.03 and afaik 9.10.

Nathan.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 17:42.