Description of problem: Reenabling the bluetooth service Version-Release number of selected component: bluez-tools-0.2.0-0.13.git20170912.7cb788c.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: bt-adapter -i crash_function: adapter_get_dbus_object_path executable: /usr/bin/bt-adapter journald_cursor: s=4868f30b45964e1f88a61743c7390a23;i=15586d;b=e40686a6fe9141d6aea47bcd636b1145;m=6118505b;t=5a32adcb676e3;x=ba63d617a3ac091b kernel: 5.6.3-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1708186
Created attachment 1678432 [details] File: backtrace
Created attachment 1678433 [details] File: core_backtrace
Created attachment 1678434 [details] File: cpuinfo
Created attachment 1678435 [details] File: dso_list
Created attachment 1678436 [details] File: environ
Created attachment 1678437 [details] File: limits
Created attachment 1678438 [details] File: maps
Created attachment 1678439 [details] File: mountinfo
Created attachment 1678440 [details] File: open_fds
Created attachment 1678441 [details] File: proc_pid_status
Similar problem has been detected: Clicked on the Bluetooth icon in the Cinnamon tray and then clicked the control to disable Bluetooth. Bluetooth appears to have been successfully disabled at that point, but a short time later the abrt problem alert appeared for bt-adapter. reporter: libreport-2.12.0 backtrace_rating: 4 cmdline: bt-adapter -i crash_function: adapter_get_dbus_object_path executable: /usr/bin/bt-adapter journald_cursor: s=f428edfb88604a459550f14bedd58bce;i=4721f;b=0002d8347a0f4cdfb1a3b11b7fa6ad04;m=1bcf1feac2;t=5a4eef579aec3;x=d1200e90ad6aa4f2 kernel: 5.6.8-300.fc32.x86_64 package: bluez-tools-0.2.0-0.13.git20170912.7cb788c.fc32 reason: bt-adapter killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp
*** Bug 1890114 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Switching the bt adapter on an off. reporter: libreport-2.13.1 backtrace_rating: 4 cmdline: bt-adapter -i crash_function: adapter_get_dbus_object_path executable: /usr/bin/bt-adapter journald_cursor: s=a37e7b54564d4c42b47936217ee036b6;i=2fb42;b=08ebe5f5225f4f448bf2dba5bba09293;m=396faf187b;t=5b2930bb9df0d;x=94bd4dd18f0f143 kernel: 5.8.15-201.fc32.x86_64 package: bluez-tools-0.2.0-0.13.git20170912.7cb788c.fc32 reason: bt-adapter killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
@kevin please assign this package to you instead of alt-gtk https://src.fedoraproject.org/rpms/bluez-tools
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.