Version-Release number of selected component: blueman-2.0.4-2.fc24 Additional info: reporter: libreport-2.7.2 cmdline: python3 /usr/bin/blueman-manager executable: /usr/bin/blueman-manager kernel: 4.7.2-201.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: errors.py:148:warp:blueman.bluez.errors.DBusFailedError: No discovery started Traceback (most recent call last): File "/usr/lib/python3.5/site-packages/blueman/bluez/errors.py", line 146, in warp return func(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blueman/bluez/Adapter.py", line 139, in stop_discovery self.get_interface().StopDiscovery() File "/usr/lib64/python3.5/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python3.5/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.Failed: No discovery started During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/blueman-manager", line 208, in <lambda> prog.connect("cancelled", lambda x: self.List.StopDiscovery()) File "/usr/lib/python3.5/site-packages/blueman/gui/DeviceList.py", line 419, in StopDiscovery self.Adapter.stop_discovery() File "/usr/lib/python3.5/site-packages/blueman/bluez/errors.py", line 148, in warp raise parse_dbus_error(exception) blueman.bluez.errors.DBusFailedError: No discovery started Local variables in innermost frame: func: <function Adapter.stop_discovery at 0x7f3723b93c80> args: (<blueman.bluez.Adapter.Adapter object at 0x7f371406beb8>,) kwargs: {}
Created attachment 1197833 [details] File: backtrace
Created attachment 1197834 [details] File: environ
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.