After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 734855 - gnome-bluetooth cannot use pin = 1234
gnome-bluetooth cannot use pin = 1234
Product: gnome-bluetooth
Classification: Core
Component: general
Other Linux
: Normal normal
: ---
Assigned To: gnome-bluetooth-general-maint@gnome.bugs
Depends on:
Reported: 2014-08-15 11:57 UTC by Alberto Salvia Novella
Modified: 2017-08-25 22:05 UTC
See Also:
GNOME target: ---
GNOME version: ---

Comment 1 Bastien Nocera 2014-08-15 12:03:36 UTC
Please put all the details in this bug report.
Comment 2 Alberto Salvia Novella 2014-08-16 11:26:17 UTC
I have a BT serial port with a pin of 1234. I cannot pair to this device with gnome-bluetooth. Every attempt results in gnome-bluetooth requiring a 6 digit random pin. I was able to pair when I uninstalled gnome-bluetooth and installed bluez-gnome. Bluez-gnome will actually send a 4 digit 1234 pin and connect. I am in the process of setting up the serial port in Ubuntu so that I can communicate with the device. My hope is that this will be fixed in Lucid so that I will not have to go through the text based setup of rfcomm for this device.

In addition, gnome-bluetooth is very reluctant to connect to the PANU served by my phone. It was set up and after a number of tries I was able to exchange PIN numbers and connect. Unfortunately, I was only able to connect to the PANU once. With bluez-gnome, it works all the time every time.

For what it is worth, the OBEX file connection to my Nokia has been very robust under either manager.

My BT dongle reports as this one:
Bus 005 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Comment 3 Bastien Nocera 2014-08-18 15:36:49 UTC
At the very least the version number of gnome-bluetooth used would be helpful, so that I know which version of BlueZ you're using as well.
Comment 4 Alberto Salvia Novella 2014-08-19 00:49:29 UTC
It seems I've made a mistake here and the bug isn't confirmed by any currently supported version downstream.

Just wait for a while since I confirm that.

Thank you.
Comment 5 Alberto Salvia Novella 2014-10-27 03:05:43 UTC
Yes, it is known to affect gnome-bluetooth version
Comment 6 Stewart Hardwick 2014-11-02 15:50:40 UTC
In addition, it doesn't appear to be limited to the 1234 PIN. If I try and set anything other than the automatic option, I still get the prompt to enter a PIN on my device. If I select one of the fixed PIN options and press Close, when I next go to the PIN options dialog the automatic option is still set.

Ubuntu 14.04 LTS (sorry, don't know how to get the version of gnome-bluetooth)
Comment 7 Alberto Salvia Novella 2014-11-02 18:49:26 UTC
@ Stewart Hardwick

As you can see in <>, the version of GNOME Bluetooth used in Ubuntu 14.04 is
Comment 8 André Klapper 2017-07-28 16:14:10 UTC
Is this still a problem 3 years later in GNOME 3.24 or 3.22?
Comment 9 Alberto Salvia Novella 2017-07-29 05:58:16 UTC
@ André Klapper

I don't know. I reported this bug on behalf of another person in (, which proved to be a bad practise.

I will ask the downstream reporter to subscribe here if they are still interested in this bug.
Comment 10 Alberto Salvia Novella 2017-07-29 06:02:01 UTC
@ André Klapper

Requested downstream: if by 2017-08-15 nobody has answered, you can close this report.

Thank you.
Comment 11 Alberto Salvia Novella 2017-07-29 06:02:54 UTC
I'm unsubscribing now, but feel free to subscribe me again if you need further info.
Comment 12 Alberto Salvia Novella 2017-07-29 06:04:19 UTC
Sorry, it seems I cannot unsubscribe. So I will be receiving follow ups anyway.
Comment 13 Eric Johnson 2017-08-19 17:27:14 UTC
This bug still exists, I can confirm on two separate setups running 16.04 LTS. I originally asked a question over on AskUbuntu about this and eventually found my way here and on the corresponding LaunchPad bug report. Is there anything I can help with on this?

Here's the question I asked this week:
Comment 14 André Klapper 2017-08-20 06:03:41 UTC
The GNOME version shipped in Ubuntu's 16.04 is two years old and upstream GNOME developers do not maintain such old versions anymore.

Can anyone still reproduce this issue with GNOME 3.24 or newer?
Comment 15 Alberto Salvia Novella 2017-08-20 17:02:23 UTC
I cannot tell myself. I reported this bug on the behalf of another user, but I don't own a bluetooth adaptor.

Moreover I quit Ubuntu and GNOME a few months ago. Now I only trust a type of project: those where developers are free to present their ideas as they wanted, but users have the final say on what option to make the default. Like a free market.

Nevertheless I will ask affected users downstream to provide the needed info here.
Comment 16 André Klapper 2017-08-21 09:15:36 UTC
Closing task as INCOMPLETE for the time being.
Comment 17 Eric Johnson 2017-08-23 05:35:10 UTC
I'd be happy to help out but I am unsure of how to proceed. Is this something I can test out with my current Ubuntu 16.04 install?

Some info:
apt list gnome-bluetooth:
gnome-bluetooth/xenial,now 3.18.2-1ubuntu2 amd64 [installed,automatic]

bluetoothctl --version:

uname -a:
Linux lyle 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Comment 18 André Klapper 2017-08-23 06:48:27 UTC
No. See comment 14.
Comment 19 Alberto Salvia Novella 2017-08-23 16:02:45 UTC
I would test with (
Comment 20 Eric Johnson 2017-08-25 21:15:14 UTC
I finally had some time to test with the mentioned live image. This is fixed in the version of gnome-bluetooth packaged with Antergos (gnome-bluetooth 3.20.1+1+ge902d1a-1). Ubuntu 16.04 packages 3.18.2 so I think this can be closed finally. It looks like 3.20 is packaged with upcoming Ubuntu versions anyways if I'm reading this page correctly

Thanks for the help.
Comment 21 Alberto Salvia Novella 2017-08-25 22:05:37 UTC
You are welcome ;)