| Summary: | bluedevil PIN never appears when adding device | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | Marc Haber <mh+kde-bugs> |
| Component: | bluetooth | Assignee: | Alex Fiestas <afiestas> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | accountlostin, gerhofer, mattmarnell, plega-kde |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/bluedevil/d402a834efe994f74fe8feb64e2dee02b4fa9a92 | Version Fixed In: | |
| Sentry Crash Report: | |||
|
Description
Marc Haber
2011-07-01 19:24:11 UTC
Hi Can you provide: 1-BlueDevil version (check your distribution package) 2-the terminal output of bluedevil-wizard Thanks! *be sure to enable all bluedevil things in kdebugdialog I have the same problem; and when I run bluedevil-wizard from the console, I eventually get a message in the console saying: Error response: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." Config: KDE Platform Version 4.6.5 (4.6.5) libbluedevil-1.9-0.1.20110502git.fc14.x86_64 bluedevil-1.1-2.fc14.x86_64 For the avoidance of doubt I should confirm that my device is a keyboard. When I try to pair with a phone it works perfectly. Maybe I'm pointing the obvious but, is your keyboard accepting connections? Also, is your keyboard a Microsoft elite? To answer the second question first, it's an Apple Wireless Keyboard (104 key model). It has new batteries and was turned on - I'm not sure there's anything I can do to demonstrate that it's accepting connections. I have tested the keyboard by booting into the Apple partition. It works fine. Under kde it recognises the keyboard but gives the screen output as described in the Description above. Git commit d402a834efe994f74fe8feb64e2dee02b4fa9a92 by Alex Fiestas. Committed on 28/04/2012 at 03:36. Pushed by afiestas into branch '1.1'. If the device is a Keyboard, move to the keyboard page. Thanks to rbelem for lettimg me steal his bt keyboard at UDS xD M +6 -5 src/wizard/pages/discoverpage.cpp http://commits.kde.org/bluedevil/d402a834efe994f74fe8feb64e2dee02b4fa9a92 this does not seem to be resolved. same problem as in the original bug report. (happens with the 'Microsoft Wedge Mobile Keyboard 7C:1E:52:1A:07:DE). another example: https://www.kubuntuforums.net/showthread.php?62281-Install-microsoft-bluetooth-wedge-keyboard&p=325382&viewfull=1#post325382 I am having the same issues with a Logitech K810. Same exact symptoms on a fresh install of OpenSUSE 13.2 w/ KDE 4.14.9. This does not appear to be fixed. I should note that this same keyboard+bluetooth+system combination works just fine OOTB with Gnome. All I have to do to make it work is open a parallel session in Gnome, and use the Gnome bluetooth setup to complete pairing. I just ran into the same issue when I tried to connect a bluetooth keyboard to KDE/OpenSuse 13.2.
The device gets discovered without issues correctly, but the password is never displayed in the KDE GUI.
I connected a HCI sniffer to the data stream (hcidump -at) and found that the keyboard is correctly sending back the password. I was able to find the passkey in the data stream:
2015-11-13 13:14:36.823350 > HCI Event: User Passkey Notification (0x3b) plen 10
bdaddr 28:18:78:FA:13:03 passkey 235802
I then typed in the passkey 235802 on the keyboard and the keyboard then connected without problems to the KDE session.
So the problem is really in KDE that does not show the passkey that gets sent back to the user. All the logic works as expected. The HCI sniffer is the workaround for everyone who finds this bug.
|