Version-Release number of selected component: bluez-5.10-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: _IO_default_xsputn executable: /usr/libexec/bluetooth/bluetoothd kernel: 3.11.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: 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] File: backtrace
Created attachment 820524 [details] File: cgroup
Created attachment 820525 [details] File: core_backtrace
Created attachment 820526 [details] File: dso_list
Created attachment 820527 [details] File: environ
Created attachment 820528 [details] File: exploitable
Created attachment 820529 [details] File: limits
Created attachment 820530 [details] File: maps
Created attachment 820531 [details] File: open_fds
Created attachment 820532 [details] File: proc_pid_status
Created attachment 820533 [details] File: var_log_messages
reproducible: always steps to reproduce: 1) put Bluetooth to discoverable mode 2) try to pair from phone to Fedora desktop result: crash 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. http://fedoraproject.org/wiki/Changes/Bluez5#Contingency_Plan
Discussed in 2013-12-09 Blocker Review meeting [1]. Voted an AcceptedFreezeException. This is a crasher in a common desktop function that may well be used on lives. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-09/
*** 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. https://admin.fedoraproject.org/updates/bluez-5.11-2.fc20
Package bluez-5.11-2.fc20: * 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: https://admin.fedoraproject.org/updates/FEDORA-2013-23113/bluez-5.11-2.fc20 then log in and leave karma (feedback).
bluez-5.12-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/bluez-5.12-1.fc20
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[770]: No agent available for request type 0 Dec 11 22:38:32 medusa bluetoothd[770]: 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[770]: No agent available for request type 0 > Dec 11 22:38:32 medusa bluetoothd[770]: device_request_pin: Operation not > permitted 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. https://admin.fedoraproject.org/updates/bluez-5.12-2.fc20
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.