kbluetoothd invalid arguments to passkey

sfrdll · 10-07-2007, 12:32 PM

Hi all,
I have a debian lenny distro and I'm trying to pair my mobile phone to the computer.
By using kbluetoothd I choose the File Exchange service: the phone asks me the PIN; I enter it and after some seconds I get a pairing error.

Looking around over the Internet I read that I had to see on the pc a popup window asking for the PIN, but that's not my case.

On the console output of kbluetoothd I get this error:

"Invalid arguments for passkey Request method"

Could anybody please help me?

many thanks
Sergio

mdg · 10-07-2007, 04:19 PM

You probably need to edit your /etc/bluetooth/hcid.conf file.

If you want to be prompted for a passkey each time, edit as follows:

Code:

# Security Manager mode
	#   none - Security manager disabled
	#   auto - Use local PIN for incoming connections
	#   user - Always ask user for a PIN
	#
	security user;

The "multi" option allows prompt-less pairing with previously paired devices:

Code:

# Pairing mode
	#   none  - Pairing disabled
	#   multi - Allow pairing with already paired devices
	#   once  - Pair once and deny successive attempts
	pairing multi;

almatic · 10-08-2007, 08:15 AM

type this and see if it works then:

passkey-agent --default /usr/lib/kdebluetooth/kbluepin

sfrdll · 10-08-2007, 01:34 PM

Thank you for your reply.

I typed the command

Quote:

passkey-agent --default /usr/lib/kdebluetooth/kbluepin

but I get the message

Quote:

Can't register passkey agent
Passkey agent already exists

my hcid.conf file follows:

Code:

#
# HCI daemon configuration file.
#

# HCId options
options {
	# Automatically initialize new devices
	autoinit yes;

	# Security Manager mode
	#   none - Security manager disabled
	#   auto - Use local PIN for incoming connections
	#   user - Always ask user for a PIN
	#
	security user;

	# Pairing mode
	#   none  - Pairing disabled
	#   multi - Allow pairing with already paired devices
	#   once  - Pair once and deny successive attempts
	pairing multi;

	# Default PIN code for incoming connections
	passkey "1234";
}

# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "%h-%d";

	# Local device class
	class 0x3e0100;

	# Default packet type
	#pkt_type DH1,DM1,HV1;

	# Inquiry and Page scan
	iscan enable; pscan enable;

	# Default link mode
	#   none   - no specific policy 
	#   accept - always accept incoming connections
	#   master - become master on incoming connections,
	#            deny role switch on outgoing connections
	lm accept;

	# Default link policy
	#   none    - no specific policy
	#   rswitch - allow role switch
	#   hold    - allow hold mode
	#   sniff   - allow sniff mode
	#   park    - allow park mode
	lp rswitch,hold,sniff,park;
}

The problem persists

almatic · 10-08-2007, 02:05 PM

then type

cat /proc/$(pgrep passkey-agent)/cmdline

and post the output.

sfrdll · 10-09-2007, 03:34 PM

Hi almatic, here is the output of your command:

/usr/bin/passkey-agent--default/usr/lib/kdebluetooth/kbluepin

almatic · 10-10-2007, 11:11 AM

I have now tried myself and can confirm this problem in both directions (phone to pc and pc to phone). hcid says something like

Code:

Passkey agent replied with an error: org.freedesktop.DBus.Error.UnknownMethod, Method "Request" with signature "ss" on interface "org.bluez.PasskeyAgent" doesn't exist

and passkey-agent gives the same error as you described. This is on a debian lenny/sid. This has worked all right some weeks ago, so it must have come in with an update.

Maybe someone else has information on the issue ...

almatic · 10-10-2007, 01:02 PM

I experimented around a bit and the only way for pairing seems to be working around the dbus passkey-agent.
Change your security mode from 'security user' to 'security auto'. Then the passkey in your hcid.conf will be accepted. This is for incoming connections only, so you have to pair from the phone to the pc.

I have also tried the package out of unstable (1.0-beta8) but this version is completely non-functional for me (doesn't find devices, doesn't connect, crashes all over).

sfrdll · 10-15-2007, 11:47 AM

Many thanks, so let's wait and hope for a future bugfix

Sergio