maemo.org Bugzilla – Bug 602
org.maemo service names do not work
Last modified: 2007-12-04 14:24:28 UTC
You need to log in before you can comment on or make changes to this bug.
On 2006 beta system having a d-bus service whose name does not start with com.nokia (such as org.maemo) gets killed by the system after a couple of seconds. Since the new documentation suggests using org.maemo prefixes, killing programs that use them is a bug. Alternately if there are some extra steps that must be taken to make these prefixes work, they should be clearly stated in the documentation.
It's now possible for the application to use 'org.maemo' prefix, but there is some code in Libosso that assumes the 'com.nokia' prefix still. So, I'll keep this still open.
This should be now fixed in Libosso v1.18 and later versions (available from Sardine): https://stage.maemo.org/svn/maemo/projects/haf/tags/libosso/1.18-1/ If you still find a bug in this, please reopen (and preferably attach a patch :)).
I just tested this on N800 and the bug still remains.
what kind of code you are using?
I tested this with my program PLCreator (https://garage.maemo.org/projects/plcreator/). To replicate simply check it out of svn. Revision 23 uses a com.nokia prefix, while revision 22 has org.maemo. This is the only difference between these two revisions. The latter gets killed by Maemo after a while, while the former keeps on running. Take these steps to build an installable deb package. ./configure make ./package.sh
Did you give "org.maemo.plcreator" as the application name to osso_initialize()?
It seems that I passed plain "plcreator" to osso_initialize. When I used com.nokia prefix elsewhere the app was not killed, whereas using org.maemo does get it killed. Whether or not this is the expected behaviour is beyond me. As far as I am concerned this bug can be closed.
Does the bug occur if you pass "org.maemo.plcreator" to osso_initialize()?
I guess it works
Closing RESOLVED and FIXED bug. No one has not touched or commented in last 180 days. If error/problem still occurs please reopen bug with comments.