Bug 1616299

Summary: bogus request for PIN entry when pairing with a mouse, cannot connect
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: gnome-bluetoothAssignee: Bastien Nocera <bnocera>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: bnocera, jmoskovc
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 22:08:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
hcidump
none
journal none

Description Chris Murphy 2018-08-15 14:31:51 UTC 
Description of problem:

When trying to connect/pair with a bluetooth mouse, the GUI asks for a PIN confirmation of 0000. Whether I click cancel or confirm, it won't connect/pair with the mouse.


Version-Release number of selected component (if applicable):
pulseaudio-module-bluetooth-12.2-1.fc28.x86_64
gnome-bluetooth-libs-3.28.1-1.fc28.x86_64
NetworkManager-bluetooth-1.10.10-1.fc28.x86_64
bluez-cups-5.50-1.fc28.x86_64
bluez-libs-5.50-1.fc28.x86_64
gnome-bluetooth-3.28.1-1.fc28.x86_64
bluez-5.50-1.fc28.x86_64
bluez-obexd-5.50-1.fc28.x86_64


How reproducible:
Always if I start out with the device removed, and try to connect/pair it cleanly. If it's already paired+trusted, it will connect maybe 90% of the time and the other 10% of the time it won't until I reboot.


Steps to Reproduce:
1. No mouse connected, paired, or trusted (remove device in GUI)
2. Gnome Settings > Bluetooth
3. Put mouse in discover+pairing mode.
4. Mouse appears in the devices list as "Not Set Up" but before I can click on that...

Actual results:

GNOME pops up a dialog asking me to confirm a PIN of 0000.


Expected results:

There should not be such a dialog, it should just blindly pair to the mouse once I've clicked on the device in the list

Additional info:

This seems to be a new behavior, I've been using this same mouse with Fedora 28 for a while and while it's sometimes flakey, pairing hasn't previously brought up a PIN dialog.
Comment 1 Chris Murphy 2018-08-15 14:32:14 UTC 
Created attachment 1476163 [details]
hcidump
Comment 2 Chris Murphy 2018-08-15 14:37:04 UTC 
Created attachment 1476166 [details]
journal

bluetoothd debugging is enabled

08:18 is the approximate time I tried to start the pairing (hcidump and journal are from the same boot so the time stamps should match up)
Comment 3 Chris Murphy 2018-08-15 14:43:10 UTC 
[mouses]# list
Controller 00:C2:C6:F0:52:57 f28h.local [default]
[mouses]# show
Controller 00:C2:C6:F0:52:57 (public)
	Name: f28h.local
	Alias: f28h.local
	Class: 0x001c010c
	Powered: yes
	Discoverable: no
	Pairable: yes
	UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0532
	Discovering: no
[mouses]# devices
Device 58:1F:AA:EB:B4:6A mouses
Device 04:52:C7:3E:7D:B3 Bose Color II SoundLink
[mouses]# 

[chris@f28h ~]$ hciconfig -a hci0
hci0:	Type: Primary  Bus: USB
	BD Address: 00:C2:C6:F0:52:57  ACL MTU: 1021:4  SCO MTU: 96:6
	UP RUNNING PSCAN 
	RX bytes:146058 acl:6600 sco:0 events:837 errors:0
	TX bytes:8481 acl:70 sco:0 commands:353 errors:0
	Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH SNIFF 
	Link mode: SLAVE ACCEPT 
	Name: 'f28h.local'
	Class: 0x1c010c
	Service Classes: Rendering, Capturing, Object Transfer
	Device Class: Computer, Laptop
	HCI Version: 4.2 (0x8)  Revision: 0x100
	LMP Version: 4.2 (0x8)  Subversion: 0x100
	Manufacturer: Intel Corp. (2)

[chris@f28h ~]$
Comment 4 Ben Cotton 2019-05-02 19:18:07 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Ben Cotton 2019-05-02 21:05:42 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Ben Cotton 2019-05-28 22:08:50 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.