Bug 1027365
| Summary: | [abrt] bluez-5.10-2.fc20: _IO_default_xsputn: Process /usr/libexec/bluetooth/bluetoothd was killed by signal 11 (SIGSEGV) | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jozef Mlich <jmlich> | ||||||||||||||||||||||||
| Component: | bluez | Assignee: | Don Zickus <dzickus> | ||||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||
| Version: | 20 | CC: | bnocera, danofsatx, dwmw2, dzickus, hhorak, kalevlember, kparal, marcel, mruckman | ||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/85fe92e50c60108e50fbac4831766e5a4b7ff1af | ||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:9bbfbb447137a55d42128575024a91db42c1db12 AcceptedFreezeException | ||||||||||||||||||||||||||
| Fixed In Version: | bluez-5.12-2.fc20 | Doc Type: | Bug Fix | ||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||
| Last Closed: | 2013-12-13 05:34:40 UTC | Type: | --- | ||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||||||||||
| Bug Blocks: | 980657 | ||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||
|
Description
Jozef Mlich
2013-11-06 16:31:10 UTC
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. |