SUMMARY A notification popped up in the right corner of the screen A Bluetooth notification asking if this is the correct pin To my surprise it happened not once, but twice And I clicked incorrect pin as many times And yet the bloody iPhone from some stranger Kept bugging my Bluetooth connection And then in my curiosity I checked my system tray And there it was that iPhone, connected, to my dismay I thought perhaps some bad poem might brighten up the mood a bit. Yes some random iPhone requested a pairing to my pc and I refused, twice. Still, the phone appeared connected in the system tray widget for some reason. I disconnected it manually from there. Not sure what, how or why this happened, nor if it is an attack vector. On my android phone the notification did not pop up twice, nor did the phone manage to connect. It seems the phone shortly appears in the tray as well but gives an error on the phone and disappears from the tray. Not sure if the iPhone person saw an error though. STEPS TO REPRODUCE 1. Have bluetooth visibility to Always Visible 2. Have some phone request a pairing 3. Click pin is incorrect in the notification 4. Check the tray OBSERVED RESULT The phone appears to be connected in the tray. EXPECTED RESULT If the pairing is denied, I expect it to not connect and not show up as connected. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.15.0-51-generic
Can you please check if the device is paired? Open the Bluetooth tray, click on the device (iPhone) and you should see "Paired: Yes/No".
Created attachment 120843 [details] Phone shows up paired (In reply to David Rosca from comment #1) > Can you please check if the device is paired? Open the Bluetooth tray, click > on the device (iPhone) and you should see "Paired: Yes/No". When I try to connect my phone this is what happens after I click the incorrect pin. The phone shows: "Pair with PC? Cancel / Pair" this keeps going for about 30 seconds. If I click Cancel or Pair the phone shows an error "couldn't pair because of bad PIN or key" pretty much. But again, the tray keeps showing the phone as connected for 30 sec while the phone just sits there until the timeout or until further action from me with results in un-pairing because of the paring was denied on the PC.
Created attachment 120844 [details] Phone shows up paired (fix)
May I ask for the first attachment to be deleted thank you. I marked it as obsolete...
You are now mixing two issues together. If you see the device as connected in the tray it doesn't actually mean that it is paired. If there is a pairing in progress, you will of course see the device as connected (otherwise it wouldn't be able to initiate the pairing). If the pairing process is not canceled/accepted after you accept/reject the PIN code, then that's a bug. But please note here, you need to accept the PIN code on both sides - on your PC and also on your phone.
(In reply to David Rosca from comment #5) > You are now mixing two issues together. > > If you see the device as connected in the tray it doesn't actually mean that > it is paired. If there is a pairing in progress, you will of course see the > device as connected (otherwise it wouldn't be able to initiate the pairing). > > If the pairing process is not canceled/accepted after you accept/reject the > PIN code, then that's a bug. But please note here, you need to accept the > PIN code on both sides - on your PC and also on your phone. For the iphone the pin request happened multiple times (twice), that is what it was weird about it. I cannot reproduce that with my android phone. The request shows once and that's it. I have no idea if that is a bug or not, I reported still.
Is it still happening in Plasma 6.2?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.