public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] hcid.conf seemingly ignored
Date: Tue, 19 Dec 2006 17:31:26 +0100	[thread overview]
Message-ID: <20061219163126.GL7959@suse.de> (raw)
In-Reply-To: <45880A1B.7030408@glidos.net>

On Tue, Dec 19, 2006 at 03:49:47PM +0000, Paul Gardiner wrote:
> Stefan Seyfried wrote:

> > Hm. It works for me. I have not configured anything via YaST, but just =
with
> > bluetooth-applet and apitest (in the bluez-test package).
> =

> I can try that: I still have the original config files I can put back in =

> place. Did you not use yast2 even to enable bluetooth?

I had the dongle plugged in during the installation, so bluetooth was
enabled by default. It should, however, just get enabled via udev when
the adapter is plugged in, even if nothing is configured.

But i did not configure anything besides "enable bluetooth" in YaST.

In 10.2, no matter how you configure it in YaST, the settings made via
DBus will override this, so no need to restore your config files IMO.
-- =

Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg  | "Well, surrounding them's out." =


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-12-19 16:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 10:12 [Bluez-users] hcid.conf seemingly ignored Paul Gardiner
2006-12-19 10:20 ` Marcel Holtmann
2006-12-19 12:28   ` Paul Gardiner
2006-12-19 15:36     ` Stefan Seyfried
2006-12-19 15:49       ` Paul Gardiner
2006-12-19 16:31         ` Stefan Seyfried [this message]
2006-12-19 17:23           ` Paul Gardiner
2006-12-19 17:37             ` Ulisses Furquim
2006-12-19 17:42             ` Stefan Seyfried
2006-12-19 17:51               ` Marcel Holtmann
2006-12-19 20:23       ` Paul Gardiner
2006-12-20  8:54         ` Stefan Seyfried
2006-12-20  9:38           ` Paul Gardiner
2006-12-20 11:04             ` Stefan Seyfried
2006-12-20 22:40               ` Paul Gardiner
2006-12-21 23:13                 ` Paul Gardiner
2006-12-22 11:06                   ` Stefan Seyfried
2006-12-22 11:18                     ` Paul Gardiner

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=20061219163126.GL7959@suse.de \
    --to=seife@suse.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