Developer FAQ

This is a list of frequently asked questions related to developing applications for the Maemo platform or working on the platform itself. This is in constant evolution, and new questions and answers are welcome.

What can I do if my question is not mentioned here?

 * 1) Look if it is discussed already in one of the mailing lists or in talk.maemo.org
 * 2) If not post your question in the developer mailing list or in talk
 * 3) If you find the answer and you think it could be interesting for others as well post it here, so that we just have to point on this page in the future if the question pops up again.

"dbus-monitor" does not work in Scratchbox. What can I do?
Error messages

Typical error messages in this case are:

X86: ~] > dbus-monitor --system Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

or for the session bus: X86: ~] > dbus-monitor Failed to open connection to session message bus: (null)

or when starting a python app: arguments to dbus_connection_get_data were incorrect, assertion "connection != NULL" failed in file dbus-connection.c GLIB ERROR ** default - Not enough memory to set up DBusConnection for use with GLib

Solution Enter the following lines in the Scratchbox:
 * Tested in Fremantle Beta, Beta_2

X86: ~] > eval $(dbus-launch --sh-syntax) X86: ~] > export BUS_SESSION_BUS_ADDRESS X86: ~] > export DBUS_SESSION_BUS_PID

Then run the dbus-monitor command and it should work fine!

"xephyr" fails to start in the host with a dbus security error
Error messages [config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.310" is not allowed to own the service "org.x.config.display2" due to security policies in the configuration file)

Solution The display you plan on using for Xephyr (typically :2) just needs to be added to the dbus security file.

You need to edit the following file: /etc/dbus-1/system.d/xorg-server.conf

Add the following three lines in the " group     

Basically you should have one for each display you plan on using, by default display 0 and display 1 are in the file. If you are planning on using a different display number for Xephyr than :2 make sure you use its number rather than "display2" when you add these lines.

How can I avoid "qemu" error messages of "af-sb-init start" in ARMEL target?
Error messages

Usually the attempt ends up with something like this:

The error was 'BadWindow (invalid Window parameter)'. (Details: serial 207 error_code 3 request_code 2 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.) aborting... qemu: uncaught target signal 6 (Aborted) - core dumped

Solution
 * all SDK's

The ARMEL target should not be used for application testing 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.

Why do I get "command not found" even though I follow the instructions in the documentation?
Error messages

As an example:

X86: ~] > af-sb-init.sh start bash: af-sb-init.sh: command not found

Solution After running the installation script you have to install some closed-source packages to have a full installation of the SDK. Most likely these are not installed. Have a look here - the last point under installation instructions - how to do that.

How to resolve "Scratchbox devkit debian-etch not found" issue?
Sometimes while running the install-script of the SDK this error occurs and produces a message like the following:

Error messages E: Scratchbox devkit debian-etch not found. E: Please complete scratchbox installation first. E: Specify an alternative installation path using '-s PATH' option.

Solution The problem can be resolved like this (with thanks to Frank Banul in the developer list):

1) add "deb http://scratchbox.org/debian/ maemo5-sdk main" to /etc/apt/sources.list 2) run: sudo apt-get remove scratchbox-devkit-debian sudo apt-get install scratchbox-devkit-debian sudo apt-get remove scratchbox-devkit-perl sudo apt-get install scratchbox-devkit-perl

Why can I reach an IP-address but no domain inside Scratchbox?
In some cases this happens because of the following reasons:
 * 1) Network configuration changed on the host-system, after Scratchbox was installed
 * 2) Scratchbox not configured correctly:
 * 3) * Manual installation of SDK was not complete
 * 4) * The target was reset

Error messages Depends on the program, which is used. But here a small test client in python:

import urllib2 print urllib2.urlopen("http://google.com").read

Then the following error message will be returned:

urllib2.URLError: 

Solution In any cases it is most likely that the resolv.conf of the Scratchbox is not set up correctly. The following solutions for this issue can solve the problem:
 * Fremantle X86(!), Diablo X86(!)


 * 1) Network configuration change: Copy the resolv.conf from the host system into the scratchbox/etc folder:

sudo cp /etc/resolv.conf /scratchbox/etc/resolv.conf

If the problem is still the same try 2.:


 * 1) Scratchbox configuration: This might be the case, if the target was reset or manual installed, without using the script. In this case run:

SBOX> sb-conf in -edFL

This sets the /scratchbox/etc/resolv.conf as default and ignores the one of the scratchbox. Info about the command you'll find here.

These steps should solve the problem. If it still does not work, you could try to replace the entries of the resolv.conf within the scratchbox with the same entries of the resolv.conf of the host system by hand.

= Script "af-sb-init.sh start" aborting = Sometimes it happens, that the script aborts just after starting. A problem might be, that old processes are still active, and cause the error. Indicator that this might be the reason are the following lines after the startup:

Indicator

_X86: ~] > af-sb-init.sh start ... 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 ... aborting...

This shows, that old processes are still running, which might cause problems in starting up the framework again.

 Solution 

To solve this stop the framework, kill all old processes and start it again. This can be done by:

~] > af-sb-init.sh stop
 * stop the framework:

~] > sb-conf killall
 * kill old processes:

~] > af-sb-init.sh start
 * restart:

How to install the SDK+ on a Linux AMD64 platform?
The Maemo SDK+ package includes scratchbox 2 and Qt, but it will only install on 32-bit platforms. If you're running Debian with a 64-bit kernel, Maemo SDK+ can be installed into a chrooted 32-bit environment that sits on top of your 64-bit platform.

Solution

This guide takes you through all the steps to the point of compilation and running the test.

QEMU error running cmake in ARMEL target in Fremantle?
Indicator qemu: uncaught target signal 11 (Segmentation fault) - core dumped make: *** [cmake_check_build_system] Error 126

 Solution  Check the version of cmake. Using version 2.6.3-2maemo4+0m5 should solve the problem.

Porting to Fremantle
This section is intended to consolidate the common errors that occur while trying to port Diablo applications to Fremantle. Feel free to improve this page and/or add additional information.

maemo-select-menu-location: command not found
Typical error message scratchbox/tools/bin/sh: line 1: /usr/sbin/dpkg-preconfigure: No such file or directory Setting up leafpad (0.8.16le-0maemo2) ... gtk-update-icon-cache: Cache file created successfully. /var/lib/dpkg/info/leafpad.postinst: line 7: maemo-select-menu-location: command not found dpkg: error processing leafpad (--configure): subprocess post-installation script returned error exit status 127

Reason

maemo-select-menu-location is obsolete. In Fremantle, there is no submenu like, "Utility", "Extra", "Settings" etc. All installed 3rd party software will be visible under "Applications" by default.

Action Remove the instance from the post installation script. It is not needed.

Missing dependency: maemo-installer-utils
Reason

The package hildon-application-manager no longer "provides" maemo-installer-utils. The commands maemo-confirm-text, maemo-application-running, maemo-list-user-packages are still available.

Action

Replace the dependency with hildon-application-manager.

Missing dependency: libhildonhelp0
Reason

libhildonhelp is dropped.

Action

Remove the dependency and calls to the help APIs.

Limitation of Home Area applets
Unlike Diablo in Fremantle these applets don't support text input, pannable areas, resizing nor scrolling.

Reason

Framework limitations.

Action

Replace text input fields with dialogs. Use buttons for scrolling. Add resizing options in the settings dialog or adapt the UI of the applet regarding to that. For further information on how to develop those applets, please check the documentation.

What icon size should be used?
With Fremantle the size specifications of the icons are different from Diablo:

Application Manager
 * Icon size: HILDON_ICON_SIZE_FINGER.
 * In Gimp or Photoshop: 48x48 pixels

Task Launcher
 * Icon size: HILDON_ICON_SIZE_THUMB.
 * In Gimp or Photoshop: 64x64 pixels

Using icons for the task launcher, please remember to run the following in your postinst file:

gtk-update-icon-cache -f /usr/share/icons/hicolor

Text and icons in dialogs
Problem

The text in dialog boxes is not formatted correctly (truncated on the right size), when a icon is in place.

Action

In general icons should not be used in dialogs in Fremantle. Remove the icon and the text will be formatted correctly.

Initialisation scripts
Problem

Initialisation scripts don't work any more.

Reason

Fremantle has switched to using upstart for system initialisation.

Action

Create upstart job definitions instead of init scripts. Information on writing these can be found on http://upstart.ubuntu.com/getting-started.html. However, be aware that the directory used on Maemo 5 is /etc/event.d.

The job script should be placed in /etc/event,d/package. And the package postinst, prerm and postrm should use the start --quiet and stop --quiet commands to start and stop the service. Unfortunately there is no debhelper tool to assist with this.

Localization isn't working
You are probably using the followin line in configure.ac:

localedir=`$PKG_CONFIG osso-af-settings --variable=localedir`

This means that you need to add osso-af-settings to your Build-Depends.

Package gets rejected: REJECTED: The same or newer version is already in extras-devel
You can't upload the same version to the repository twice. If you have changed anything in your package, you should increase your version number or package revision.

Build failed: No such file or directory in log file
You probably forgot to specify the correct Build-Depends in debian/control. The autobuilder starts every build with a clean SDK image. If you need any application during building which is not available in the default SDK image, you need to specify it specifically.

You may verify that your Build-Depends field in debian/control is complete by running

dpkg-depcheck -m dpkg-buildpackage -rfakeroot -b

in the source tree. (You'll need to  for this to work).

Build failed, works in my own scratchbox
See the answer above.

How do I request upload rights for Extras
You can request an invitation via the Extras Assistant.