linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Bluez mailing list <linux-bluetooth@vger.kernel.org>
Subject: bluetoothd Discovery caching changes?
Date: Fri, 23 Feb 2018 12:24:40 +0100	[thread overview]
Message-ID: <1519385080.29059.4.camel@hadess.net> (raw)

Hey,

Some time ago, it seems that bluetoothd's caching got more aggressive,
and I now end up with devices listed in GNOME's Bluetooth Settings that
never seem to go away, including ones without any service or type data.

I usually have devices where pairing was attempted without success, or
were used once but not paired or trusted, being stuck in the list.
Discovered devices also stay around for a long time.

This causes problems in busy environment, as despite security advices,
tons of Bluetooth devices are visible in offices, and half-discovered
(got a bdaddr, but no SDP info) devices are still visible long after
they're gone.

Is this the expected behaviour? If we had information about when the
device was discovered, or when it was added, it would make it easier to
clean up that cache in the front-ends.

Cheers

                 reply	other threads:[~2018-02-23 11:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1519385080.29059.4.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).