Bug#754830: Info received (Second part of bug not fixed)

2014-08-12 Thread Dean Hamstead
possibly the rfcomm sections can simply be removed as they seem to be a 
convenience only?


'rfcomm bind all' is no longer valid, also 'rfcomm unbind' is similarly 
no longer a valid command


as binding is now per-device, it seems this should be config option in 
the defaults file?


On Wed, 30 Jul 2014 00:15:23 +0200 Andreas Eriksson 
 wrote:

Hi again.

It seems that "rfcomm bind all" isn't a thing that works in bluez 5.x, 
by
design, so I think that the bug here as far as debian is concerned is 
that

the init script tries to run rfcomm at all. You now have to run rfcomm
  for each connection individually, the command 
doesn't

accept 'all'.

The reason my device doesn't work with 5.x seems more likely to be 
because
it uses bluez-alsa and the bluez-alsa version in sid is still 4.x and 
not

5.x.



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#754830: Info received (Second part of bug not fixed)

2014-07-29 Thread Andreas Eriksson
Hi again.

It seems that "rfcomm bind all" isn't a thing that works in bluez 5.x, by
design, so I think that the bug here as far as debian is concerned is that
the init script tries to run rfcomm at all. You now have to run rfcomm
  for each connection individually, the command doesn't
accept 'all'.

The reason my device doesn't work with 5.x seems more likely to be because
it uses bluez-alsa and the bluez-alsa version in sid is still 4.x and not
5.x.