I'm leaning towards these keyboards being rather finicky. I've got an
aluminum bt keyboard. When I try to pair, look at this bluetoothd
output:
bluetoothd[6925]: Temporary agent registered for hci0/00:1B:63:FA:CD:5A at
:1.132:/org/bluez/agent/wizard
bluetoothd[6925]: adapter_get_device(00:1B:63
I tried again, after I was convinced it really was in discovery mode,
and the device worked fine. It asked me for entering the pin, and I'm
typing on it right now.
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug
I have one of the white keyboards that predates the aluminum ones. I had
it working fine using hidd and the hci reset method described in the
blog post I mentioned in the bug description.
I have had trouble with this keyboard ever since the bluetooth stack was
overhauled for Hardy. I used the act
Previous Bug:
https://bugs.edge.launchpad.net/ubuntu/+source/bluez-utils/+bug/191704
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I have removed Mactel support from this bugreport, because it's not
related to Apple devices only. I have Microsoft Bluetooth Mouse with the
same problem. And - NO problems with older Ubuntu having hidd. Just type
hidd --connect AA:BB... and everything works (forever).
New wizard behaviour:
- Conn
I'm leaning towards these keyboards being rather finicky. I've got an
aluminum bt keyboard. When I try to pair, look at this bluetoothd
output:
bluetoothd[6925]: Temporary agent registered for hci0/00:1B:63:FA:CD:5A at
:1.132:/org/bluez/agent/wizard
bluetoothd[6925]: adapter_get_device(00:1B:63
I tried again, after I was convinced it really was in discovery mode,
and the device worked fine. It asked me for entering the pin, and I'm
typing on it right now.
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug
I have one of the white keyboards that predates the aluminum ones. I had
it working fine using hidd and the hci reset method described in the
blog post I mentioned in the bug description.
I have had trouble with this keyboard ever since the bluetooth stack was
overhauled for Hardy. I used the act
Previous Bug:
https://bugs.edge.launchpad.net/ubuntu/+source/bluez-utils/+bug/191704
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I have removed Mactel support from this bugreport, because it's not
related to Apple devices only. I have Microsoft Bluetooth Mouse with the
same problem. And - NO problems with older Ubuntu having hidd. Just type
hidd --connect AA:BB... and everything works (forever).
New wizard behaviour:
- Conn
I'm leaning towards these keyboards being rather finicky. I've got an
aluminum bt keyboard. When I try to pair, look at this bluetoothd
output:
bluetoothd[6925]: Temporary agent registered for hci0/00:1B:63:FA:CD:5A at
:1.132:/org/bluez/agent/wizard
bluetoothd[6925]: adapter_get_device(00:1B:63
I tried again, after I was convinced it really was in discovery mode,
and the device worked fine. It asked me for entering the pin, and I'm
typing on it right now.
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug
I have one of the white keyboards that predates the aluminum ones. I had
it working fine using hidd and the hci reset method described in the
blog post I mentioned in the bug description.
I have had trouble with this keyboard ever since the bluetooth stack was
overhauled for Hardy. I used the act
I have removed Mactel support from this bugreport, because it's not
related to Apple devices only. I have Microsoft Bluetooth Mouse with the
same problem. And - NO problems with older Ubuntu having hidd. Just type
hidd --connect AA:BB... and everything works (forever).
New wizard behaviour:
- Conn
Previous Bug:
https://bugs.edge.launchpad.net/ubuntu/+source/bluez-utils/+bug/191704
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I'm leaning towards these keyboards being rather finicky. I've got an
aluminum bt keyboard. When I try to pair, look at this bluetoothd
output:
bluetoothd[6925]: Temporary agent registered for hci0/00:1B:63:FA:CD:5A at
:1.132:/org/bluez/agent/wizard
bluetoothd[6925]: adapter_get_device(00:1B:63
I tried again, after I was convinced it really was in discovery mode,
and the device worked fine. It asked me for entering the pin, and I'm
typing on it right now.
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug
I have one of the white keyboards that predates the aluminum ones. I had
it working fine using hidd and the hci reset method described in the
blog post I mentioned in the bug description.
I have had trouble with this keyboard ever since the bluetooth stack was
overhauled for Hardy. I used the act
I have removed Mactel support from this bugreport, because it's not
related to Apple devices only. I have Microsoft Bluetooth Mouse with the
same problem. And - NO problems with older Ubuntu having hidd. Just type
hidd --connect AA:BB... and everything works (forever).
New wizard behaviour:
- Conn
Previous Bug:
https://bugs.edge.launchpad.net/ubuntu/+source/bluez-utils/+bug/191704
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I'm leaning towards these keyboards being rather finicky. I've got an
aluminum bt keyboard. When I try to pair, look at this bluetoothd
output:
bluetoothd[6925]: Temporary agent registered for hci0/00:1B:63:FA:CD:5A at
:1.132:/org/bluez/agent/wizard
bluetoothd[6925]: adapter_get_device(00:1B:63
I tried again, after I was convinced it really was in discovery mode,
and the device worked fine. It asked me for entering the pin, and I'm
typing on it right now.
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug
I have one of the white keyboards that predates the aluminum ones. I had
it working fine using hidd and the hci reset method described in the
blog post I mentioned in the bug description.
I have had trouble with this keyboard ever since the bluetooth stack was
overhauled for Hardy. I used the act
I have removed Mactel support from this bugreport, because it's not
related to Apple devices only. I have Microsoft Bluetooth Mouse with the
same problem. And - NO problems with older Ubuntu having hidd. Just type
hidd --connect AA:BB... and everything works (forever).
New wizard behaviour:
- Conn
Previous Bug:
https://bugs.edge.launchpad.net/ubuntu/+source/bluez-utils/+bug/191704
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I'm leaning towards these keyboards being rather finicky. I've got an
aluminum bt keyboard. When I try to pair, look at this bluetoothd
output:
bluetoothd[6925]: Temporary agent registered for hci0/00:1B:63:FA:CD:5A at
:1.132:/org/bluez/agent/wizard
bluetoothd[6925]: adapter_get_device(00:1B:63
I tried again, after I was convinced it really was in discovery mode,
and the device worked fine. It asked me for entering the pin, and I'm
typing on it right now.
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug
I have one of the white keyboards that predates the aluminum ones. I had
it working fine using hidd and the hci reset method described in the
blog post I mentioned in the bug description.
I have had trouble with this keyboard ever since the bluetooth stack was
overhauled for Hardy. I used the act
I have removed Mactel support from this bugreport, because it's not
related to Apple devices only. I have Microsoft Bluetooth Mouse with the
same problem. And - NO problems with older Ubuntu having hidd. Just type
hidd --connect AA:BB... and everything works (forever).
New wizard behaviour:
- Conn
Previous Bug:
https://bugs.edge.launchpad.net/ubuntu/+source/bluez-utils/+bug/191704
--
[Intrepid] New Bluetooth Wizard fails to pair with Apple Keyboard...
https://bugs.launchpad.net/bugs/281580
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Hi,
meba:
> I consider this critical and I believe this should focus on reenabling
> hidd as the new stack seems to be buggy for advanced users. Really - can
> it cause a lot of pain to beginners if they have hidd?
The real problem with hidd is that the "hidd --connect" workaround is
"good enough
Hi,
meba:
> I consider this critical and I believe this should focus on reenabling
> hidd as the new stack seems to be buggy for advanced users. Really - can
> it cause a lot of pain to beginners if they have hidd?
The real problem with hidd is that the "hidd --connect" workaround is
"good enough
Hi,
meba:
> I consider this critical and I believe this should focus on reenabling
> hidd as the new stack seems to be buggy for advanced users. Really - can
> it cause a lot of pain to beginners if they have hidd?
The real problem with hidd is that the "hidd --connect" workaround is
"good enough
Hi,
meba:
> I consider this critical and I believe this should focus on reenabling
> hidd as the new stack seems to be buggy for advanced users. Really - can
> it cause a lot of pain to beginners if they have hidd?
The real problem with hidd is that the "hidd --connect" workaround is
"good enough
Hi,
meba:
> I consider this critical and I believe this should focus on reenabling
> hidd as the new stack seems to be buggy for advanced users. Really - can
> it cause a lot of pain to beginners if they have hidd?
The real problem with hidd is that the "hidd --connect" workaround is
"good enough
Hi,
meba:
> I consider this critical and I believe this should focus on reenabling
> hidd as the new stack seems to be buggy for advanced users. Really - can
> it cause a lot of pain to beginners if they have hidd?
The real problem with hidd is that the "hidd --connect" workaround is
"good enough
36 matches
Mail list logo