On 2015-03-03 01:57:24, Christopher Schramm wrote:
> Hi Antoine,
>
> unfortunately BlueZ 5's generic connect method is a misconception in my
> eyes as in your case it will not connect the NAP service. In the current
> upstream master you will not get a generic connect item in the menu
> anymore, but see which services are provided and could be connected with
> it. In case of Android phones there typically exists some audio service
> that should be connectible, but fails with that error message. It may
> just be that the device needs to be in a specific state (e.g. have a
> media app running) to make the connection work.
>
> Anyway, connecting to a NAP should work. You just have to select the
> service from the device menu and not use the generic connect item for that.
There's no service from the menu, in fact, the "Serial server" menu item
is gone.
There's only a "connect" option which simply fails.
And this is not an android phone, this is a LG flip phone.
>> I insist on pointing out this is a regression from Wheezy and should
>> really be fixed before jessie is released, hence the "grave" severity
>> above.
>
> That's not correct as...
>
>> I would
>> seriously consider downgrading back to the stable version (1.23) while
>> upstream works on 2.0, which seems to be more in an alpha state.
>
> This wouldn't bring us anywhere as 1.23 does not support BlueZ 5 at all.
Understood. Upstream seems to be saying they fixed this peculiar
problem in git (although the milestone item says the contrary), maybe a
git snapshot should be tried in experimental?
A.
--
Be who you are and say what you feel
Because those who mind don't matter
And those who matter don't mind.
- Dr. Seuss
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
