| 1 |
On Tue, Feb 18, 2014 at 10:14 AM, Ralf |
| 2 |
<ralf+gentoo@×××××××××××××××××××.de> wrote: |
| 3 |
> On 02/18/14 17:10, Canek Peláez Valdés wrote: |
| 4 |
> |
| 5 |
> systemctl status bluetooth.service |
| 6 |
> |
| 7 |
> |
| 8 |
> Yes, sure, as I wrote above. |
| 9 |
> |
| 10 |
> Active: active (running) since Tue 2014-02-18 16:57:05 CET; 15min ago |
| 11 |
> |
| 12 |
> ps auxw|grep bluetoot |
| 13 |
> root 3571 27.6 0.0 21200 2112 ? Rs 16:57 4:29 |
| 14 |
> /usr/libexec/bluetooth/bluetoothd |
| 15 |
> |
| 16 |
> As you see everything is actually running fine... I even tried to restart it |
| 17 |
> several times |
| 18 |
|
| 19 |
OK, sorry, I hadn't read carefully your first post. blueman-applet |
| 20 |
fails because it uses the 4.x dbus API from bluez. gnome-bluetooth |
| 21 |
uses the 5.x dbus API, and AFAIK, right now it's the only tool using |
| 22 |
it. |
| 23 |
|
| 24 |
So, with gnome-bluetooth you can detect your keyboard but the pairing |
| 25 |
fails? You say you paired the keyboard correctly with your android |
| 26 |
phone; you don't need to do something in the keyboard to pair it to a |
| 27 |
different hosts? Something like keep pressing the power button? |
| 28 |
|
| 29 |
Regards. |
| 30 |
-- |
| 31 |
Canek Peláez Valdés |
| 32 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 33 |
Universidad Nacional Autónoma de México |
Archives