From: "RISKÓ Gergely" <gergely@risko.hu>
To: linux-bluetooth@vger.kernel.org
Cc: Context Devel mailing list <context-devel@projects.maemo.org>
Subject: [PATCH] bluez git HEAD doesn't put introspection methods into the introspection output
Date: Tue, 01 Sep 2009 17:10:08 +0300 [thread overview]
Message-ID: <87eiqq3ge7.fsf@bubble.risko.hu> (raw)
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
Hi,
I have the following problem:
4252@17:04 errge@lisa:~$ qdbus --system org.bluez
/
Cannot introspect object / at org.bluez:
org.freedesktop.DBus.Error.UnknownInterface (Interface 'org.freedesktop.DBus.Introspectable' was not found)
This is caused by the fact that:
- QtDBus is buggy as hell, :)
- BlueZ doesn't include introspection API in the introspection output.
Either of the causes got solved, the whole issue is solved. After
checking the code of QtDBus I decided to go with the second. See the
attached patch. After applying it everything works fine:
4252@17:04 errge@lisa:~$ qdbus --system org.bluez
/
/org
/org/bluez
/org/bluez/9746
/org/bluez/9746/any
/org/bluez/9746/hci0
/org/bluez/test
If you need clarification or have comments about any of these, please
don't hesitate to reply!
Thanks in advance,
Gergely
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: bluez-introspection.diff --]
[-- Type: text/x-diff, Size: 802 bytes --]
diff --git a/gdbus/object.c b/gdbus/object.c
index 3186921..8091a95 100644
--- a/gdbus/object.c
+++ b/gdbus/object.c
@@ -156,6 +156,11 @@ static void generate_introspection_xml(DBusConnection *conn,
gstr = g_string_new(DBUS_INTROSPECT_1_0_XML_DOCTYPE_DECL_NODE);
g_string_append_printf(gstr, "<node name=\"%s\">\n", path);
+ g_string_append_printf(gstr, "\t<interface name=\"org.freedesktop.DBus.Introspectable\">\n");
+ g_string_append_printf(gstr, "\t\t<method name=\"Introspect\">\n");
+ g_string_append_printf(gstr, "\t\t\t<arg name=\"xml_data\" type=\"s\" direction=\"out\"/>\n");
+ g_string_append_printf(gstr, "\t\t</method>\n");
+ g_string_append_printf(gstr, "\t</interface>\n");
for (list = data->interfaces; list; list = list->next) {
struct interface_data *iface = list->data;
next reply other threads:[~2009-09-01 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 14:10 RISKÓ Gergely [this message]
2009-09-02 10:00 ` [PATCH] Add introspection interface to the output of introspection calls RISKÓ Gergely
2009-09-02 14:46 ` Luiz Augusto von Dentz
2009-09-02 17:48 ` RISKÓ Gergely
2009-09-14 14:18 ` Johan Hedberg
2009-09-14 14:52 ` RISKÓ Gergely
2009-09-14 21:11 ` Johan Hedberg
2009-09-15 10:50 ` Luiz Augusto von Dentz
2009-09-15 12:28 ` RISKÓ Gergely
2009-09-15 15:22 ` Johan Hedberg
2009-09-15 17:27 ` Marcel Holtmann
2009-09-15 17:55 ` Johan Hedberg
2009-09-15 19:25 ` RISKÓ Gergely
2009-09-16 11:07 ` RISKÓ Gergely
2009-09-16 11:39 ` Johan Hedberg
2009-09-16 12:03 ` RISKÓ Gergely
2009-09-24 17:22 ` Johan Hedberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eiqq3ge7.fsf@bubble.risko.hu \
--to=gergely@risko.hu \
--cc=context-devel@projects.maemo.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox