From: Adam Tauno Williams <adam@morrison-ind.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Anyone got bluez working?
Date: Mon, 24 Sep 2007 08:30:38 -0400 [thread overview]
Message-ID: <1190637038.5490.0.camel@aleph.wmmi.net> (raw)
In-Reply-To: <1190617562.5133.86.camel@aeonflux.holtmann.net>
[-- Attachment #1.1: Type: text/plain, Size: 769 bytes --]
> > I'm new here and I'd like to point out that after the version 3.12 nothing got
> > working.
> > Actually I've install Version 3.19, but I can't figure out anything right.
> > Most of the time the deamon on d-bus isn't answering and pairing don't
> > happen. The pin-helper no way, passkey-agent giving up and no pairing.
> > Pls show me one of your configuration that works. I always on KDE desktop and
> > also Kbluetooth has several problems to be solved, but even by bash I can't
> > get done.
> no idea what you are trying to do, but I know for sure that the latest
> Fedora, Ubuntu and openSuSE work perfectly fine. And their upcoming
> releases have even the latest versions in it.
Yep, using openSUSE 10.2/GNOME and Bluetooth works great.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-09-24 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 19:03 [Bluez-users] Anyone got bluez working? Fulvio
2007-09-24 7:06 ` Marcel Holtmann
2007-09-24 12:30 ` Adam Tauno Williams [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=1190637038.5490.0.camel@aleph.wmmi.net \
--to=adam@morrison-ind.com \
--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