https://bugs.kde.org/show_bug.cgi?id=475959
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Connecting to phone via |Provide more human friendly |Bluetooth applet fails to |message when device |work unless first |connection fails with no |attempting to connect to |message |the phone's PAN using the | |Networks applet | Severity|normal |wishlist --- Comment #10 from TraceyC <[email protected]> --- Thanks for the logs, those are helpful. It looks like you tried to connect to the smartphone, and nothing happened, so you tried a second time and got the error that an attempt was already in progress. I also see a lot of chatter from the bluetooth controller on your system, which appears to be producing an unusual amount of change events. This looks like a problem in the bluetooth stack, that Plasma isn't responsible for. Typically this is an issue with the device definition that gets parsed by upstream code; please report to https://github.com/bluez/bluez/issues. Thanks! Also, the problem with the notification that says nothing other than the phone's identifier is all that bluetoothctl is providing to Plasma, so that's all that's in the message. Something actionable for KDE would be to provide a more useful message when the bluetooth connect event produces no information, along the lines of "Failed to connect to <device name and ID>. The bluetooth system failed to provide a reason". I'm sure the developers can come up with something useful here. -- You are receiving this mail because: You are watching all bug changes.
