Description of problem: bluetoothd crashed while manually connect to a bluetooth mouse. Version-Release number of selected component (if applicable): kernel 4.17.0-0.rc6.git1.1.fc29.x86_64 bluez-5.49-3.fc28.x86_64 How reproducible: Random - seems to happen more often after resuming from suspend-to-RAM and the mouse and laptop refuse to automatically connect, so I go into GNOME settings > bluetooth to manually connect. Sometimes that works. Sometimes bluetoothd crashes. Steps to Reproduce: 1. Gnome settings > bluetooth 2. Click on already paired mouse 3. Flip the connection switch from off to on Actual results: Crash Expected results: No crash Additional info: https://marc.info/?l=linux-bluetooth&m=152726289605394&w=2 [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 ISCAN RX bytes:2296642 acl:114596 sco:0 events:653 errors:0 TX bytes:8710 acl:233 sco:0 commands:208 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)
Created attachment 1441673 [details] dmesg
Created attachment 1441674 [details] gdb stack trace
Created attachment 1441675 [details] journal all journalctl -b -o short-monotonic
Created attachment 1441676 [details] journal, k message only journalctl -k -o short-monotonic Should be the same as dmesg but this file is a bit bigger so there may be more stuff in it.
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.
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.