From: tmp@nitwit.de
To: Bluez-users@lists.sourceforge.net
Subject: [Bluez-users] You may replace bluez's pin helper...
Date: Thu, 28 Apr 2005 20:42:44 +0200 [thread overview]
Message-ID: <200504282042.44428.tmp@nitwit.de> (raw)
Hi!
Despite I put the line (pinhelper /usr/lib/kdebluetooth/kbluepin) in hcid.conf
and commented the orginal line the windows asking me for doing so still comes
up...
Well, anything I may have forgotten? And yes,the path to the file is correct.
I'm on gentoo 2005.0
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-04-28 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 18:42 tmp [this message]
2005-04-28 19:18 ` [Bluez-users] You may replace bluez's pin helper Fred Schaettgen
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=200504282042.44428.tmp@nitwit.de \
--to=tmp@nitwit.de \
--cc=Bluez-users@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