Bug#384379: [Pkg-bluetooth-maintainers] Bug#384379: WORK-AROUND for "iscan not set"

[Marcel Holtmann]

Hi Filippo,

> > > Yes, maybe correct grammatical mistakes if present.
> > > Note that deleting the "config" file in /var/lib/bluetooth is an essential 
> > > part of the solution.
> > 
> > this is a big _NO_. Don't mess with the configuration storage directly.
> > The configuration storage has priority over the hcid.conf file and this
> > is meant to be this way.
> > 
> > The "iscan" and "pscan" config option are some legacy option that are
> > still available for some strange corner cases for some embedded distros
> > and they are not meant for general and permanent configuration.
> 
> Marcel, can you confirm the actual solution is the one you indicated in
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384379#msg10 ?
> 
> Jaime, could you please retry as well? bluez 3.7 is both in testing and
> unstable.

actually adding "discovto 0" as default in hcid.conf is fine. That is a
decision the distros can make. And it seems that most of them are doing
this at the moment.

> > If people don't learn that hcid.conf are proposed default values for the
> > cold run only, then I might simply remove the whole file in the next
> > upstream release. So stop writing ugly distribution specific hacks and
> > better ask upstream for it. There might might a real bug hiding
> > somewhere.
> 
> If hcid.conf values are there only for a cold run I think it needs to be
> documented, I didn't found anything in hcid.conf(5) though, is it documented
> somewhere?

It should be documented. If not, then that is the real bug here. Feel
free to send in patches for the manual pages.

Regards

Marcel