No PIN request - no pairing possible

[Hadmut Danisch]

Hi,

I can't pair the ubuntu notebook with mobile phones, since there is no request for a pin. Neither the bluez-pin, nor the gnome applet works.

However, the gnome applet still displays a message when the bluez utils are restarted, so it works in principle. dbus-monitor does not show anything that looks like a PIN request, so that might be the problem.

regards
Hadmut

[Marcel Holtmann (holtmann)]

The request for entering a passkey are not D-Bus signals. So you might wanna start "hcidump -X -V" to capture the traffic on the HCI and check if a pairing request really happens.

[Hadmut Danisch (hadmut)]

Marcel Holtmann wrote:
> The request for entering a passkey are not D-Bus signals. So you might
> wanna start "hcidump -X -V" to capture the traffic on the HCI and check
> if a pairing request really happens.

Sure it happens. It happened and worked well the last > 2 years as long
as bluez was calling the PIN requester directly. And the mobile itself
also asks for the Passkey.

It is just that there is currently no way to enter the key.

Maybe you'd give a summary how entering the key is expected to work,
then I could start debugging.

All I found is that the old way to configure to directly call bluez-pin
in hcid.conf does not work anymore, but I did not find any description
about what should happen right now.

regards
Hadmut

[Marcel Holtmann (holtmann)]

If you log into the GNOME desktop, the passkey agent will ask you to enter the PIN code and everything will work as expected. With the latest updated packages you will see a Bluetooth icon in the status bar and you need to click it to open the input dialog for the PIN. Otherwise check /var/log/syslog for error messages from hcid.

[Ori Avtalion (salty-horse)]

I am not seeing any bluetooth icon in the status bar.
I'm using hcid's security=user mode, which should prompt me for a new PIN with each connection attempt.

When trying to connect from my phone to the computer, I get the phone's "enter PIN" dialog, and after I enter one and fail to connect, the following is printed to /var/log/syslog:
hcid: pin_code_request (sba=<bdaddr>, dba=<bdaddr>)
hcid: call_passkey_agent(): no agent registered

Installing bluez-passkey-gnome resolved it (note: I had to run "bt-applet --sm-disable" myself since /etc/xdg/autostart/bt-applet.desktop didn't autostart - is this a bug?)

[dvo (mueller8)]

This is how I got the PIN popup working for feisty: call (even as a normal user)
  passkey-agent --default /usr/bin/bluez-pin
before initiating the connection. This will register bluez-pin as the pin helper,
as you may check with "tail -f /var/log/syslog"

N.B. Including in /etc/bluetooth/hcid.conf a line like
  pin_helper /usr/bin/bluez-pin;
does not help - for some reason, this option is not recognized any more :(

[Fredrik Wendt (fredrik-wendt)]

Confirming this issue - this used to work in dapper. A permanent workaround would be nice.

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Andreas Moog (ampelbein)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to "New". Thanks again!

 status invalid

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiuj+UACgkQ06FgkPZwicSqrACcDw6zBy8ZSP6x5/UdcjOrRSsA
tSkAoN2fNuYecE5NivJlXJVGU+I9DOq7
=XGDB
-----END PGP SIGNATURE-----

[lsmod (forum+ubuntu)]

I have the same problem that it is not possible to pair my PC with a Samsung mobile.
I can search for the mobile and it will be found and added to the list.

But when i right-click the device and select pairing (kopplung) a pop-up window "pairing request" appears, but i can't enter a pin.
There is a blinking cursor but i can't do anything with this window.

I am using Lucid on AMD64.

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for posting this bug.

Does this occur in Maverick?

[lsmod (forum+ubuntu)]

Sorry i have no installation of Maverick at this time.

Has a bug fixing happen regarding this problem?

How can i analyze the problem in Lucid?

[rusivi2 (rusivi2-deactivatedaccount)]

In Lucid, the package is called gnome-bluetooth, but you can access it via clicking System -> Preferences -> Bluetooth and if your computer has a bluetooth device either internal or external it should be auto-sensed and have at it!

lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04

apt-cache policy gnome-bluetooth
gnome-bluetooth:
  Installed: 2.30.0-0ubuntu3
  Candidate: 2.30.0-0ubuntu3
  Version table:
 *** 2.30.0-0ubuntu3 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

[lsmod (forum+ubuntu)]

Yes of course - but i didn't asked for support how to start with bluetooth.

I am using an external Bluetooth stick (ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter)
and this is working without problem with the right devices.
So i can connect without problems for instance with an Sony/Ericsson mobile.
It is working and it is possible to transfer pictures or videos.

But it is not working with all devices!
When i try to connect to a Samsung mobile it can be seen, but the pairing fails as i described.

The question is why?
And how can i debug the process of pairing on the shell or in log-files?

[rusivi2 (rusivi2-deactivatedaccount)]

lsmod thank you for responding so quickly and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Regarding gnome-bluetooth and your samsung mobile, there have been many changes in Ubuntu since the time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could check for a similar problem via https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth and, if none are relevant, please test your installation of Lucid via clicking Applications -> Accessories -> Terminal, then typing in it:

ubuntu-bug gnome-bluetooth

and any other logs that are relevant to this issue. bluez-utils has not been updated since Hardy so regarding this bug it seems it should be closed. Thank you again and feel free to send me a link of the gnome-bluetooth bug you find or bug yourself as we want to see your matter resolved!

[Launchpad Janitor (janitor)]

[Expired for bluez-utils (Ubuntu) because there has been no activity for 60 days.]