Bug#384379: [Pkg-bluetooth-maintainers] Bug#384379: WORK-AROUND for
"iscan not set"
Jaime Alberto Silva
jaimealbertosilva at gmail.com
Wed Jan 3 04:52:54 CET 2007
Hi everyone,
On 12/31/06, Filippo Giunchedi <filippo at debian.org> wrote:
> Hello,
>
> On Sun, Dec 31, 2006 at 01:36:21PM +0100, Marcel Holtmann wrote:
> > > 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.
I've been using "discovto 0;" in hcid.conf without any problems for a while.
Currently I'm using bluez 3.7-1, there was an update a while ago when
I had to add the line again to hcid.conf to make it work, and since
then I tell debconf not to modify my hcid.conf in the updates so I
can't tell if this version doesn't have the bug.
>
> >
> > 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?
>
> thanks,
> filippo
AFAIK the only thing needed to get the behaviour I want is to add
"discovto 0;" to hcid.conf the problem was that I didn't found that
in the manuals so I think that updating the hcid.conf manual is a
solution to the bug, and it will be nice to add a default value with a
comment to the package's hcid.conf, something like:
...
# Set the time in seconds the discovery mode will be enabled, change
to 0 to keep it forever
discovto 180;
...
> --
> Filippo Giunchedi - http://esaurito.net
--
Jaime Alberto Silva
More information about the Pkg-bluetooth-maintainers
mailing list