Description of problem: attempting to pair with bluetooth trackball Version-Release number of selected component: blueman-2.1-0.8.alpha2.fc27 Additional info: reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-assistant --device=C8:47:8C:27:90:1A crash_function: callback exception_type: GLib.GError executable: /usr/bin/blueman-assistant kernel: 4.15.3-300.fc27.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: Base.py:90:callback:blueman.bluez.errors.DBusInProgressError: Operation already in progress Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/blueman/bluez/Base.py", line 81, in callback value = proxy.call_finish(result).unpack() GLib.GError: g-io-error-quark: GDBus.Error:org.bluez.Error.InProgress: Operation already in progress (36) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/blueman/bluez/Base.py", line 90, in callback raise parse_dbus_error(e) blueman.bluez.errors.DBusInProgressError: Operation already in progress Local variables in innermost frame: error: None reply: None result: <Gio.Task object at 0x7f52779e4bd0 (GTask at 0x55f8013d6b80)> proxy: <Adapter.Adapter object at 0x7f52779e41f8 (blueman+bluez+Adapter+Adapter at 0x55f80110d610)>
Created attachment 1397887 [details] File: backtrace
Created attachment 1397888 [details] File: cgroup
Created attachment 1397889 [details] File: cpuinfo
Created attachment 1397890 [details] File: environ
Created attachment 1397891 [details] File: mountinfo
Created attachment 1397892 [details] File: namespaces
Created attachment 1397893 [details] File: open_fds
Similar problem has been detected: I was simply clicking on the BT status icon to see what package provided the BT functionality. My new BT mouse has started to lag badly. When I first connected it, it worked fine. I put the laptop to sleep, and upon waking, I had a lot of trouble connecting to the mouse again. Removed the BT mouse device and re-paired. Now the mouse is laggy. No real solutions on the internet for similar behavior. This is with Fedora 27 on a Dell XPS15. reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-assistant crash_function: callback exception_type: GLib.GError executable: /usr/bin/blueman-assistant kernel: 4.15.14-300.fc27.x86_64 package: 1:blueman-2.1-0.8.alpha2.fc27 reason: Base.py:90:callback:blueman.bluez.errors.DBusInProgressError: Operation already in progress runlevel: N 5 type: Python3 uid: 600
Similar problem has been detected: plug in usb bluetooth adapter reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-manager crash_function: callback exception_type: GLib.GError executable: /usr/bin/blueman-manager kernel: 4.16.7-200.fc27.x86_64 package: 1:blueman-2.1-0.8.alpha2.fc27 reason: Base.py:90:callback:blueman.bluez.errors.DBusInProgressError: Operation already in progress runlevel: N 5 type: Python3 uid: 1000
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.