https://bugs.kde.org/show_bug.cgi?id=358753
--- Comment #6 from David Rosca ---
Sorry but no, it would be only guessing.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358753
--- Comment #5 from arne anka ---
but according to the log snippet, the pairing request is handled through
bluedevil -- wouldn't it be possible to use that as a distinguishing feature?
incoming/pending pairing request of unknown device -> "pairing reque
https://bugs.kde.org/show_bug.cgi?id=358753
--- Comment #4 from David Rosca ---
(In reply to arne anka from comment #3)
> but maybe to show a dedicated name for that pairing phase, different from
> "connected" would be helpful?
But there is no way to distinguish it, BlueZ just reports connected.
https://bugs.kde.org/show_bug.cgi?id=358753
--- Comment #3 from arne anka ---
i see, thanks for the info.
but maybe to show a dedicated name for that pairing phase, different from
"connected" would be helpful?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358753
--- Comment #2 from David Rosca ---
And one last thing, the only thing you can do is to set your adapter to Hidden.
There is no other way to stop other devices initiate pairing with your adapter.
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=358753
David Rosca changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
