EDIT: Alright, so it looks like I'm missing an agent. I finally found out about bluetoothctl, and when I registered agent KeyboardOnly; default-agent there, it worked! Now what do I have to do to make it usable via GUI? Plus it seems like blueman has some major bugs, anyway... attempting to connect results in an empty error message, and I can't receive files, because it's using an outdated DBUS interface for OpenObex, and obexfs fails silently... yay for userfriendliness! Imagine what a newbie would do in that situation...
EDIT2: OK, giving up. _Not even_ the stable or testing versions work together after purging and reinstalling everything about Bluetooth, they're _all_ incompatible. Even though I now managed to connect (have bluetoothctl running with keyboard agent, enter yes on connection attempt), and even though it registers like 10 services from the BlackBerry, _only_ the remote control service is allowed. When I try it the other way around, with obexftp, I have to specify the precise channel to connect on so that it doesn't just report "Connecting...failed: connect", and _then_ it times out with "Connecting..\failed: send UUID". (Plus the usual _real helpful_ messages like "error: connect(): success".) And even getting _that_ far would have been completely impossible without extensive console work. I've never seen something that thoroughly riddled with holes, because you can't call those bugs any more. 15 years of using Linux, and I can't get a simple Bluetooth transfer set up in several hours? Right, right, we're past the 90s, it's the year of the Linux Desktop...
==================================
Hi!
I'm trying to pair my old BlackBerry 8310 to my Linux desktop (up-to-date Debian Sid, 3.15-10.dmz.1-liquorix-amd64) by using blueman and its associated tools. Scanning for the device works equally well for both sides; however, I am unable to pair the two once it comes to entering the PIN.
If I scan from my PC, I have two options in blueman-manager regarding my phone: Directly selecting "pair", or selecting "setup".
- If I select "pair", nothing happens on my desktop, but the phone asks me to enter a PIN; if I do so, it reports that pairing has failed. During that, nothing is logged to the console.
- Selecting "setup" opens a configuration dialog that allows for entering or generating a PIN. Regardless, I get to a screen that tells me to enter the PIN on the phone, and at the same time, the phone pops up the equivalent dialog. This would be what one would expect to work; but whatever I enter (naturally, the same on both), both devices report that pairing has failed, and blueman-manager logs
Code:
init_services (/usr/lib/python2.7/dist-packages/blueman/main/Device.py:73)
Loading services
org.bluez.Error.AuthenticationFailed: Authentication Failed
- If I instead try to pair from the phone, I cannot see any kind of reaction from my desktop - all I get is the equivalent "pairing failed" message from the BlackBerry after I entered a PIN in the dialog that pops up there.
hcitool scan and hciconfig -a work without complaints, but I cannot find a way to try the pairing as a whole on the console since bluez-simple-agent seems to have been discontinued and this recommendation is everywhere on Google. (Plus everyone only worries about pairing _without_ PIN...) hcitool cc as root opens the PIN dialog on the phone, then fails with "Input/Output error" once I enter it. The user is not permitted to execute this command. I also tried creating /usr/lib/bluetooth/<MAC>/pincodes to manually define a persistent PIN, which seems to have had no effect. The same goes for running the different commands as root, though I'm really confused about the internal structure of the Bluetooth subsystem now: They usually and inconsistently failed with Python or DBUS errors or just showed the same results.
The only other Bluetooth device I have around are a pair of Creative speakers. Trying "setup" asks me to enter a key on them, which is impossible. If I try "pair", I'm asked for a PIN as I should, but no pairing takes place, and no errors appear on the console. (It just repeats their name a few times.) Interestingly, I tried that before writing my question, and nothing happened in terms of PIN questions, just like with the BlackBerry, which still shows no change. I don't think I actively changed anything since then. The BlackBerry can pair with and connect to the speakers, and everything goes as one would expect, so the problem is definitely with my desktop.
So thus my questions:
- What is that PIN window generated by, and why does it seem to appear randomly?
- How can I find out what, exactly, fails after trying to add the speakers, as this may give me a clue?
- Is there any kind of complete log that concerns itself with Bluetooth?
- What data can I provide to make this more solvable?
Thanks,
V
