* bluetoothd Discovery caching changes?
@ 2018-02-23 11:24 Bastien Nocera
0 siblings, 0 replies; only message in thread
From: Bastien Nocera @ 2018-02-23 11:24 UTC (permalink / raw)
To: Bluez mailing list
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-02-23 11:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-23 11:24 bluetoothd Discovery caching changes? Bastien Nocera
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).