All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fred Schaettgen <bluez-user@schaettgen.de>
To: bluez-users@lists.sourceforge.net, tmp@nitwit.de
Subject: Re: [Bluez-users] You may replace bluez's pin helper...
Date: Thu, 28 Apr 2005 21:18:02 +0200	[thread overview]
Message-ID: <200504282118.02456.bluez-user@schaettgen.de> (raw)
In-Reply-To: <200504282042.44428.tmp@nitwit.de>

On Thursday, 28. April 2005 20:42, tmp@nitwit.de wrote:
> 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.

You forgot to post this to the right mailinglist. kdebluetooth != BlueZ
Simply check the "Don't show again" checkbox below the message. It's just an 
unconditional advertisement popup for kdebluetooth's pin helper. You are free 
to use whichever you want. Maybe the wording sounds a bit too demanding, but 
I never thought this might be a problem for anyone.

Fred

-- 
Fred Schaettgen
bluez-devel@schaettgen.de


-------------------------------------------------------
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

      reply	other threads:[~2005-04-28 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 18:42 [Bluez-users] You may replace bluez's pin helper tmp
2005-04-28 19:18 ` Fred Schaettgen [this message]

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=200504282118.02456.bluez-user@schaettgen.de \
    --to=bluez-user@schaettgen.de \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=tmp@nitwit.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.