From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [Bluez-devel] dbus pin failure From: David Woodhouse To: bluez-devel@lists.sourceforge.net In-Reply-To: <1141666471.4733.3.camel@aeonflux.holtmann.net> References: <1141396234.8699.10.camel@localhost.localdomain> <1141397987.12964.23.camel@aeonflux.holtmann.net> <1141418085.8699.23.camel@localhost.localdomain> <1141532537.4871.9.camel@aeonflux.holtmann.net> <1141663646.4110.60.camel@pmac.infradead.org> <1141666471.4733.3.camel@aeonflux.holtmann.net> Content-Type: text/plain Message-Id: <1141683988.29230.3.camel@localhost.localdomain> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 06 Mar 2006 22:26:28 +0000 On Mon, 2006-03-06 at 18:34 +0100, Marcel Holtmann wrote: > so I assume this means that bluez-pin is at fault. Actually that is > out of my responsibility. Do you have a sample PIN helper which is known to work? My dbus-fu is weak; it would help if dbus wasn't a moving target :) -- dwmw2 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel