From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Some bluez-gnome 1.2 bugs
Date: Fri, 05 Sep 2008 09:51:47 +0200 [thread overview]
Message-ID: <48C0E513.1040304@free.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
Hi all,
I just started to play recently with bluez 4.x.
I found at least two very annoying bugs in the bluez-gnome-1.2 wizard:
- On my debian testing system, the wizard does not allow me to enter
the pin code. The pin code just gets displayed a fraction of second an
then disappears. As a consequence the default 123456 pin code gets used
and pairing fails.
- If i try to go back to the first wizard page where my bluetooth
device is displayed, it is already selected. I have no way to go to the
next page : the next button stays grey whatever i do. (screenshot attached).
Cheers,
Fabien
[-- Attachment #2: snap.png --]
[-- Type: image/png, Size: 17817 bytes --]
[-- Attachment #3: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2008-09-05 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 7:51 Fabien Chevalier [this message]
2008-09-05 16:58 ` [Bluez-devel] Some bluez-gnome 1.2 bugs Marcel Holtmann
2008-09-08 17:37 ` Fabien Chevalier
2008-09-08 18:06 ` Marcel Holtmann
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=48C0E513.1040304@free.fr \
--to=fabchevalier@free.fr \
--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 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.