Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#5764 - bt-applet does not spring up pairing window on request

Attached to Project: Arch Linux
Opened by Eugenia Loli-Queru (Eugenia) - Monday, 06 November 2006, 01:25 GMT
Last edited by Thomas Bächler (brain0) - Friday, 14 September 2007, 12:25 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

hcitool cc 00:03:2F:26:12:8C
hcitool auth 00:03:2F:26:12:8C

does not load up the gnome-bluetooth dialog that sits in my notification area to ask me for a pin number. Here's my hcid.conf (the system does not have a /usr/bin/bluepin btw)

The /etc/bluetooth/pin has 0000 in it.


# 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;

# PIN helper
pin_helper /usr/bin/bluepin;

# D-Bus PIN helper
dbus_pin_helper;
}

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

# Local device class
# class 0x3e0100;
class 0x120104;

# 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;

# Authentication and Encryption (Security Mode 3)
auth enable;
encrypt enable;

I have also enabled discoverability of my laptop, but still, when I request a pairing via hcitool auth, this does not happen via the GUI.
This task depends upon

Closed by  Thomas Bächler (brain0)
Friday, 14 September 2007, 12:25 GMT
Reason for closing:  None
Additional comments about closing:  Several new versions have been released, no feedback has been provided on these and the bug could not be reproduced by anyone else.
Comment by Thomas Bächler (brain0) - Monday, 06 November 2006, 21:37 GMT
The icon in the tray should start flashing and by clicking on it, a dialog should be opened. Is this the case?
Comment by Eugenia Loli-Queru (Eugenia) - Monday, 06 November 2006, 21:38 GMT
No, it is not. It does not flash when I ask for authorization.
Comment by Eugenia Loli-Queru (Eugenia) - Monday, 06 November 2006, 21:39 GMT
I do the request by:
hcitool cc 00:03:2F:26:12:8C
hcitool auth 00:03:2F:26:12:8C

I need the Arch laptop initiate the pairing.
Comment by arjan timmerman (blaasvis) - Saturday, 11 November 2006, 12:00 GMT
works perfect for me.
Comment by arjan timmerman (blaasvis) - Saturday, 11 November 2006, 12:46 GMT
try :right click -> preferences -> mode op operation -> set it to visible and connectable for other devices and put make invisible to never.
Comment by Eugenia Loli-Queru (Eugenia) - Saturday, 18 November 2006, 07:12 GMT
gnome-obex-send does not work. It does not find my PocketPc which is in discoverability mode.

Regarding the hcitool, it only works the FIRST time. It loads the bluetooth window, i enter 0000, then I go to my pocketpc, I enter there 0000, but it does NOT pair. Retrying to do this again does NOT work. The gnome window does not load up the second time.

Also, I don't think that your default /etc/bluetooth/hcid.conf is helpful at all. For example, it tries to find "pin_helper bluepin" which simply does not exist anymore. This has been superseded by a new binary, can't remember its name.

Please spend more time with your bluetooth packages and do extensive testing. Things just don't work out of the box after you have the right packages installed and the bt service loaded. The hcid.conf needs fixing.
Comment by Eugenia Loli-Queru (Eugenia) - Tuesday, 28 November 2006, 06:40 GMT
Anyone tried this yet? Come on, all you have to do is put your phone in pairing mode and try to send a file via Nautilus' "send via bluetooth" option and see if that window finds your phone or something.
Comment by Thomas Bächler (brain0) - Tuesday, 28 November 2006, 08:48 GMT
It all works perfectly here. I suggest you get help from the forums, this is a butracker and not a support center.
Comment by Eugenia Loli-Queru (Eugenia) - Tuesday, 28 November 2006, 20:44 GMT
Well, it doesn't work here. It doesn't find my PDA at all and I have to KILL that window in order to make it go away. To me, this sounds like a bug, not a support issue.

Loading...