<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi Sudheer,<br>Yes, I had a similar use-case and faced the same problem. <br><br>I ensured that my daemon was properly "osso-initialised" to ensure that its triggered properly by gui-app via dbus-daemon successfully. <br><br>But, in your use-case, you seem to use QT. I am not aware of the fix.<br><br>Regards,<br>Chitti<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div class="plainMail"><br>Message: 27<br>Date: Fri, 7 May 2010 23:26:18 -0700<br>From: Scifi Guy <<a ymailto="mailto:scifi.guy@hotmail.com" href="/mc/compose?to=scifi.guy@hotmail.com">scifi.guy@hotmail.com</a>><br>Subject: RE: Noob question re Qt Application structure<br>To: <<a ymailto="mailto:dottedmag@dottedmag.net" href="/mc/compose?to=dottedmag@dottedmag.net">dottedmag@dottedmag.net</a>><br>Cc: Maemo Dev Mailing List <<a
ymailto="mailto:maemo-developers@maemo.org" href="/mc/compose?to=maemo-developers@maemo.org">maemo-developers@maemo.org</a>><br>Message-ID: <<a ymailto="mailto:BLU146-W207510D72DFAA65E43C698FCF70@phx.gbl" href="/mc/compose?to=BLU146-W207510D72DFAA65E43C698FCF70@phx.gbl">BLU146-W207510D72DFAA65E43C698FCF70@phx.gbl</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br><br>>> Twas brillig at 10:05:38 07.05.2010 UTC-07 when <a ymailto="mailto:scifi.guy@hotmail.com" href="/mc/compose?to=scifi.guy@hotmail.com">scifi.guy@hotmail.com</a><br>>> did gyre and gimble:<br>>> <br>>> SG> Could you please elaborate what you mean by "upon first access"?<br>>> <br>>> There is elaborate documentation.<br>>> <br>>> <a href="http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services"
target="_blank">http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services</a><br>>> <br>>> -- <br>>> <a href="http://fossarchy.blogspot.com/" target="_blank">http://fossarchy.blogspot.com/</a><br><br>>Thank you :) <br>><br>>I will create the service for the daemon and post back the results. Probably tonight (at work now). <br>><br>>Thank you all for taking time to read and respond to my post.<br>><br>>~Sudheer<br> <br>I am back with my questions again. Not sure If I need to start a new thread but let me ask anyway.<br><br>I have split my functionality into two apps, one running as a daemon and another as a GUI app. Now, I am trying send dbus signals to daemon. Till now I am not successful. Could you guys tell me what am I doing wrong
here?<br><br>Here is my /usr/share/dbus-1/services/org.maemo.vicar.service file content<br><br># Service description file<br>[D-BUS Service]<br>Name=org.maemo.vicar<br>Exec=/home/user/vicar-daemon<br><br># Code from the cpp file<br> if (!connection.registerService("org.maemo.vicar")) {<br> qDebug() << dbusUtility.getErrorMessage();<br> exit(1);<br> }<br><br> if (!connection.registerObject("/org/maemo/vicar", this,<br> QDBusConnection::ExportScriptableSlots)) {<br> qDebug() << dbusUtility.getErrorMessage();<br> exit(2);<br> }<br><br>1) If I reboot the device, the service does not get activated automatically. I verified this by running the method call org.freedesktop.DBus.ListNames (on System Bus). But If I run the executable
manually, the service is registered successfully to system bus and I can see the name listed with the method call org.freedesktop.DBus.ListNames. Why is the daemon not launched automatically?<br><br>2) The daemon app connects to a custom signal on launch. <br> <br> QDBusConnection connection = QDBusConnection::systemBus();<br><br> bool success = connection.connect(QString(""),<br> QString(""),<br> QString("org.maemo.vicar"),<br> QString("startOutgoingCallMonitor"),this,<br> SLOT(startOutgoingCallMonitor()));<br><br>I am receiving the boolean value as successful. With the app
running, I tried to send the Dbus signal from terminal. I am not successful so far. Could you tell me what is wrong here?<br><br>~ $ dbus-send --system --print-reply --type=signal --dest=org.maemo.vicar org/maemo/vicar org.maemo.vicar.startOutgoingCallMonitor<br>process 1686: arguments to dbus_message_new_signal() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1165.<br>This is normally a bug in some application using the D-Bus library.<br>Couldn't allocate D-Bus message<br> <br></div></blockquote></td></tr></table><br>