Hide Forgot
Version-Release number of selected component: blueman-2.1-0.3.git7a2e20e.fc23 Additional info: reporter: libreport-2.6.4 cmdline: python3 /usr/bin/blueman-manager executable: /usr/bin/blueman-manager kernel: 4.4.7-300.fc23.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: errors.py:148:warp:blueman.bluez.errors.DBusNotReadyError: Resource Not Ready Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/blueman/bluez/errors.py", line 146, in warp return func(*args, **kwargs) File "/usr/lib/python3.4/site-packages/blueman/bluez/Adapter.py", line 47, in remove_device self._interface.RemoveDevice(device.get_object_path()) File "/usr/lib64/python3.4/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python3.4/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.NotReady: Resource Not Ready During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/blueman/gui/manager/ManagerDeviceMenu.py", line 336, in <lambda> item.connect("activate", lambda x: self.Blueman.remove(device)) File "/usr/bin/blueman-manager", line 220, in remove self.List.Adapter.remove_device(device.Device) File "/usr/lib/python3.4/site-packages/blueman/bluez/errors.py", line 148, in warp raise parse_dbus_error(exception) blueman.bluez.errors.DBusNotReadyError: Resource Not Ready Local variables in innermost frame: kwargs: {} func: <function Adapter.remove_device at 0x7f724f2c61e0> args: (<Adapter object at 0x7f724c071d38 (blueman+bluez+Adapter+Adapter at 0x557c6b595380)>, <Device object at 0x7f724c07cbd0 (blueman+bluez+Device+Device at 0x557c6b685500)>)
Created attachment 1150185 [details] File: backtrace
Created attachment 1150186 [details] File: environ
*** Bug 1329924 has been marked as a duplicate of this bug. ***
Similar problem has been detected: The module stops working on a regular basis most of the time when I start my computer... reporter: libreport-2.6.4 cmdline: python3 /usr/bin/blueman-manager executable: /usr/bin/blueman-manager kernel: 4.5.6-200.fc23.x86_64 package: blueman-2.1-0.3.git7a2e20e.fc23 reason: errors.py:148:warp:blueman.bluez.errors.DBusNotReadyError: Resource Not Ready runlevel: N 5 type: Python3 uid: 1000
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** Bug 1350270 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.