Description of problem: This problem occurs everytime when I start the blueman and the bluetooth is not turned on. Blueman creates a pop-up window and asks to "Enable bluetooth" and when I click on it, blueman crashes. This never happened when starting blueman with bluetooth on. How reproducible: always when bluetooth is OFF Actual results: blueman crashes Expected results: blueman starts Version-Release number of selected component: 1:blueman-2.1-0.11.alpha3.fc28 Additional info: reporter: libreport-2.9.5 cmdline: /usr/bin/python3 /usr/bin/blueman-manager crash_function: __init__ exception_type: AttributeError executable: /usr/bin/blueman-manager interpreter: python3-3.6.8-2.fc28.x86_64 kernel: 4.20.11-100.fc28.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: ManagerStats.py:21:__init__:AttributeError: 'NoneType' object has no attribute 'get_object_path' Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/blueman/main/Manager.py", line 138, in on_dbus_name_appeared self.Stats = ManagerStats(self) File "/usr/lib/python3.6/site-packages/blueman/gui/manager/ManagerStats.py", line 21, in __init__ self.hci = adapter_path_to_name(blueman.List.Adapter.get_object_path()) AttributeError: 'NoneType' object has no attribute 'get_object_path' Local variables in innermost frame: blueman: <Manager.Blueman object at 0x7f0890fd3240 (blueman+main+Manager+Blueman at 0x556820ab2530)> self: <blueman.gui.manager.ManagerStats.ManagerStats object at 0x7f088a2e7978> Potential duplicate: bug 1668128
Created attachment 1548863 [details] File: backtrace
Created attachment 1548864 [details] File: cgroup
Created attachment 1548865 [details] File: cpuinfo
Created attachment 1548866 [details] File: environ
Created attachment 1548867 [details] File: mountinfo
Created attachment 1548868 [details] File: namespaces
Created attachment 1548869 [details] File: open_fds
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 will be EOL soon. Please upgrade to Fedora 29 or Fedora 30. On the new Fedoras, there's a new version of blueman, 2.1.beta1, currently in testing. https://bodhi.fedoraproject.org/updates/?packages=blueman Please check out the testing version, or wait until it reaches stable, and check if the error still occurs.
Hi Artur, I installed the blueman-2.1-0.15.beta1.fc29.x86_64 version and now blueman crashes before even asking to 'Enable Bluetooth'.
Ok, now it did ask to Enable Bluetooth but it crashes anyway. But it seems that only the GUI part (blueman-manager I am guessing) is crashing. There are other processes that start - blueman-applet and blueman-tray. And my device gets connected. The only thing that seems to have some problems is the GUI.
FEDORA-2019-8c57291079 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-8c57291079
FEDORA-2019-0829cd8aca has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-0829cd8aca
blueman-2.1-0.17.beta1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-8c57291079
blueman-2.1-0.16.beta1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-0829cd8aca
FEDORA-2019-e615964e0e has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e615964e0e
FEDORA-2019-716095d88b has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-716095d88b
blueman-2.1-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e615964e0e
blueman-2.1-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-716095d88b
blueman-2.1-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
blueman-2.1-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.