From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hidd binary removed form bluez-utils package unable to connect as a result
Date: Wed, 16 Apr 2008 08:33:58 +0200 [thread overview]
Message-ID: <48059DD6.2060900@suse.de> (raw)
In-Reply-To: <BLU102-W21AA1F8EAA92E59B0CCE37A6EA0@phx.gbl>
Alexandre O'Hara schrieb:
> Hi to all developpers,
> =
> I'm a 3rd party user. I would like to thank you all for the work you've d=
one so far.
> =
> I also would like to point you to this bug in case you were not already a=
ware of it : https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/191=
704
I did not read that bug completely (was there any information in there? If
yes, i could not find it). But everything works just fine without hidd here=
. I
can manage my input devices with kdebluetooth's input wizards, and i know t=
hat
people are using the bluez-gnome applet to connect input devices (have not
tried it for some time now, but i am positive that it works).
-- =
Stefan Seyfried
R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg)
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference =
Don't miss this year's exciting event. There's still time to save $100. =
Use priority code J8TL2D2. =
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/java=
one
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-04-16 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 0:46 [Bluez-devel] hidd binary removed form bluez-utils package unable to connect as a result Alexandre O'Hara
2008-04-16 6:33 ` Stefan Seyfried [this message]
2008-04-16 15:22 ` Alexandre O'Hara
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=48059DD6.2060900@suse.de \
--to=seife@suse.de \
--cc=bluez-devel@lists.sourceforge.net \
/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