From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
In-Reply-To: <48C0E513.1040304@free.fr>
References: <48C0E513.1040304@free.fr>
Date: Fri, 05 Sep 2008 18:58:31 +0200
Message-Id: <1220633911.6714.86.camel@californication>
Mime-Version: 1.0
Subject: Re: [Bluez-devel] Some bluez-gnome 1.2 bugs
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

Hi Fabien,

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

I am working on improving the PIN handling way, but at the same time I
have to make sure that it works with Simple Pairing and in the most
simple way. It is not that easy.

Also for some devices the PIN code needs to be random instead of 123456.

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

Hold shift while selecting to unselect and then select again. I know
that this is broken.

Regards

Marcel


-------------------------------------------------------------------------
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=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel