Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 _IO_default_xsputn at genops.c:447
#1 _IO_vfprintf_internal at vfprintf.c:1316
#2 ___vsprintf_chk at vsprintf_chk.c:85
#3 ___sprintf_chk at sprintf_chk.c:31
#4 sprintf at /usr/include/bits/stdio2.h:33
#5 ba2str at lib/bluetooth.c:79
#6 btd_adapter_confirm_reply at src/adapter.c:4672
#7 confirm_cb at src/device.c:3963
#8 agent_unref at src/agent.c:227
#9 confirm_cb at src/device.c:3967
Created attachment 820523 [details]
Created attachment 820524 [details]
Created attachment 820525 [details]
Created attachment 820526 [details]
Created attachment 820527 [details]
Created attachment 820528 [details]
Created attachment 820529 [details]
Created attachment 820530 [details]
Created attachment 820531 [details]
Created attachment 820532 [details]
Created attachment 820533 [details]
steps to reproduce:
1) put Bluetooth to discoverable mode
2) try to pair from phone to Fedora desktop
This bug is caused by following change: http://fedoraproject.org/wiki/Changes/Bluez5
If I knew about this month sooner, I had proposed to follow the contingency plan, as described here: http://fedoraproject.org/wiki/Changes/Bluez5#Contingency_Plan
Change owners, please try to fix this bug soon as possible in after Final release updates.
Proposed as a Freeze Exception for 20-final by Fedora user martix using the blocker tracking app because:
Result of broken Bluez5 Change, it's too late to switch back to Bluez4. At least, we should have Freeze Exception for this.
Discussed in 2013-12-09 Blocker Review meeting . Voted an AcceptedFreezeException. This is a crasher in a common desktop function that may well be used on lives.
*** Bug 1039690 has been marked as a duplicate of this bug. ***
bluez-5.11-2.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing bluez-5.11-2.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
bluez-5.12-1.fc20 has been submitted as an update for Fedora 20.
It doesn't crash for me with bluez-5.12-1.fc20. I can pair PC->phone, but the opposite direction does not work. This is in the log:
Dec 11 22:38:32 medusa bluetoothd: No agent available for request type 0
Dec 11 22:38:32 medusa bluetoothd: device_request_pin: Operation not permitted
(In reply to Kamil Páral from comment #19)
> It doesn't crash for me with bluez-5.12-1.fc20. I can pair PC->phone, but
> the opposite direction does not work. This is in the log:
> Dec 11 22:38:32 medusa bluetoothd: No agent available for request type 0
> Dec 11 22:38:32 medusa bluetoothd: device_request_pin: Operation not
That means that you don't have something like gnome-shell, or a Bluetooth applet running.
I'm using gnome-shell and gnome-bluetooth is installed. What else can be missing?
bluez-5.12-2.fc20 has been submitted as an update for Fedora 20.
bluez-5.12-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
bluez-5.12-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.