From: Marcel Holtmann <marcel@holtmann.org>
To: "Liu, Raymond" <raymond.liu@intel.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Can we change org.openobex.Client's dbus node path?
Date: Mon, 24 Nov 2008 04:30:50 +0100 [thread overview]
Message-ID: <C0D77808-B8E7-4BF3-81D8-52EE39667C6C@holtmann.org> (raw)
In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E0217AA44@pdsmsx502.ccr.corp.intel.com>
Hi Raymond,
>> Also I don't see your issue here. So you are saying that within obex-
>> client when you introspect / that you are not getting /org in the
>> list
>> of paths.
>>
>
> Yes, can not get /org in the node list for org.openobex.client
this is a bug in gdbus then. The exactly same code is used in
bluetoothd and connmand so it seems weird. Did you try to debug it
where it actually fails to get this wrong? Are we missing some
"invalidate parent" calls?
Regards
Marcel
next prev parent reply other threads:[~2008-11-24 3:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 2:01 Can we change org.openobex.Client's dbus node path? Liu, Raymond
2008-11-24 2:41 ` Marcel Holtmann
2008-11-24 3:24 ` Liu, Raymond
2008-11-24 3:30 ` Marcel Holtmann [this message]
2008-11-24 5:39 ` Liu, Raymond
2008-11-24 5:48 ` Liu, Raymond
2008-11-24 8:29 ` Marcel Holtmann
2008-11-24 10:11 ` Liu, Raymond
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=C0D77808-B8E7-4BF3-81D8-52EE39667C6C@holtmann.org \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=raymond.liu@intel.com \
/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