testing four devcies here resulted in exactly one working (hey, thats at
least one more than with 3.x)
* foldable bluetooth freedom keyboard .
- In HID mode: gets seen, but there is no way for me to input the device
sided hardcoded PIN at the host, instead the host seems to generate a PIN and
requires me to input something device side (which is not supported))
- In SPP mode: makes bluetoothd segfault immediately on scan, sadly no
apport integration to easily get a backtrace
* navilock gps reciever:
- Makes bluetoothd segfault immediately on scan, no way for me to input the
device sided hardcoded PIN at the host, instead the host seems to generate a
PIN and requires me to input something device side (which is not supported at
the device as it has no keypad)
* jabra BT headset:
- pairs, generates the device hardcoded 0000 PIN, but alsa complains about
not being able to set a proper bitrate using the test mentioned in the
announcement mail
* motorola razor mobile phone
- pairs, host generates a PIN, PIN is accepted, fully browserable
generally: i found the icons less than intuitive, it is not clear if the
button ith the plug is for connect or disconnect, it is not clear what
the star is for (tooltips FTW ;) )
--
Look into switching to bluez 4.x
https://bugs.launchpad.net/bugs/274950
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
