So I finally figured out how to avoid triggering this problem. The clue was from dmesg:
[ 4130.799255] Bluetooth: hci0: last event is not cmd complete (0x0f) Which finally led me to changing in /etc/default/tlp the following line from 0 to 1 : # Bluetooth devices are excluded from USB autosuspend: # 0=do not exclude, 1=exclude. USB_BLACKLIST_BTUSB=1 Which seems to do the trick. This means that for me the problem is fixed. However, the tlp package is specific to Thinkpads and the prevalence of at least the "last event is not cmd complete" line on the net would suggest that other systems can be similarly afflicted. The crash triggered here is too obscure to let the average user make the connection to USB autosuspend. So there really should be some more helpful error message for this form of interaction resulting from USB misconfiguration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765860 Title: blueman-browse crashed with blueman.bluez.errors.DBusInProgressError in warp(): Operation already in progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1765860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
