pavelmachek (pavelmachek) wrote,

hcid is now infected with dbus -- in Debian

...and that's ungood, if you are trying to connect to internet using GPRS/UMTS over bluetooth. (if you try to start ppp, you need to enter pin code on both phone and PC... which you can't do without dbus).

Theres /usr/share/doc/bluez-utils/examples/passkey-agent.c ... but unless you are dbus developer, you probably don't have neccessary headers... which you can't download without network, which will not connect without dbus.

Apparently, debian maintainer tried to be a bit helpful:

Note to the tech-savy:
If you are stuck in console and absolutely need to pair with yourbluetooth device have a look at
/var/lib/bluetooth//pincodes. Please note that
this mode of operation is _not_ _supported_. Don't mess with files in
/var/lib/bluetooth/ unless you know what you are doing. I repeat:manually adding a pincode for a remote device is NOT SUPPORTED.

...unfortunately I could not figure pincodes format, it is not documented on the manpage, and you can't google without network, which will not connect without dbus.

I tried to initiate pairing from phone, where hcid is apparently allowed to use pincode from hcid.conf... (Why can't the same pincode be optionaly used for outgoing stuff? From what I see, I'm far from alone falling into this trap.) Unfortunately computer did not seem to be discoverable.

After long search, I managed to "hciconfig hci0 piscan"... which made computer discoverable and solved my problems. Dbus sucks, and whoever infected hcid with it should be forced to use only GPRS networking for next 10 years.
  • Post a new comment


    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.