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!
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!
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
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
|
Detailshcitool 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.
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.
hcitool cc 00:03:2F:26:12:8C
hcitool auth 00:03:2F:26:12:8C
I need the Arch laptop initiate the pairing.
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.