From: Joachim Breitner <nomeata@debian.org>
To: Filippo Giunchedi <filippo@debian.org>
Cc: 498056@bugs.debian.org, smartphones-userland@linuxtogo.org,
linux-bluetooth@vger.kernel.org
Subject: Re: Bug#498056: Can not control input_service via dbus
Date: Sun, 07 Sep 2008 15:20:43 +0200 [thread overview]
Message-ID: <1220793643.3366.36.camel@otto.ehbuehl.net> (raw)
In-Reply-To: <20080907104334.GD30302@clamp.esaurito.net>
[-- Attachment #1: Type: text/plain, Size: 2122 bytes --]
[CC’ing linux-bluetooth, maybe you can tell us what’s happening]
Hi,
Am Sonntag, den 07.09.2008, 12:43 +0200 schrieb Filippo Giunchedi:
> On Sun, Sep 07, 2008 at 11:50:12AM +0200, Joachim Breitner wrote:
> > > that explains the bug, unless I'm missing something of course :)
> >
> > it does indeed, but then I wonder why this functionality is present in
> > an openembedded based image for the FreeRunner that runs (supposedly)
> > bluez-utils 3.23-r2, which is older than what’s in Debian, and I can not
> > find any patches regarding this...
> >
> > And indeed, looking at:
> > http://shr.bearstech.com/sources/bluez-utils-3.23.tar.gz
> > The above code lines are filled with some functionality!
> >
> > So looking in the changelog, I see:
> > ver 3.32:
> > [..]
> > Remove HAL support helpers.
> > Remove inotify support.
> > Remove service daemon activation handling.
> > Remove uneeded D-Bus API extension.
> >
> > Interesting. Do you have any idea why this was removed? Is there some
> > replacement functionality?
>
> Judging from the code above my first guess (offhand) is because services migrated
> from external processes to plugins (loaded via g_module_load).
>
> Unfortunately I'm unaware of any replacement (though I have not checked the new
> 4.x code)
I’m not sure. I think the dbus interface already is part of the new
plugin based stuff? Also, if I disable the plugin (DisablePlugins=input
in /etc/bluetooth/main.conf), the whole /org/bluez/service_input dbus
interface disappears.
The relevant diff in upstream’s CVS does unfortunately not tell us more
about why this was removed:
http://bluez.cvs.sourceforge.net/bluez/utils/hcid/dbus-service.c?r1=1.151&r2=1.152
So I CC’ed upstream: Would you please explain us why this dbus interface
was disabled, and what’s supposed to replace it?
Thanks everyone,
Joachim
--
Joachim "nomeata" Breitner
Debian Developer
nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
parent reply other threads:[~2008-09-07 13:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20080907104334.GD30302@clamp.esaurito.net>]
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=1220793643.3366.36.camel@otto.ehbuehl.net \
--to=nomeata@debian.org \
--cc=498056@bugs.debian.org \
--cc=filippo@debian.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=smartphones-userland@linuxtogo.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