After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 689530 - privacy: implement 'visible over bluetooth'
privacy: implement 'visible over bluetooth'
Status: RESOLVED WONTFIX
Product: gnome-control-center
Classification: Core
Component: Privacy
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on: 685717
Blocks:
 
 
Reported: 2012-12-03 13:39 UTC by Matthias Clasen
Modified: 2016-02-01 15:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthias Clasen 2012-12-03 13:39:48 UTC 
The privacy panel design
https://live.gnome.org/Design/SystemSettings/Privacy
has a switch for 'visible over bluetooth'. That should do more or less the same as the existing 'discoverable' switch in the bluetooth panel, I think. Implementation needed.
Comment 1 Bastien Nocera 2012-12-18 10:54:55 UTC 
As mentioned on IRC, this is more complicated to implement than the Visible switch in the Bluetooth panel.

The visible switch in the Bluetooth panel only changes the visibility for the default Bluetooth adapter, not for all the adapters. Also, by default, adapters are not visible, so plugging in any new Bluetooth device will make it invisible, whatever the default value for it.

Making it depend on the BlueZ 5 migration, as code changes would be necessary there, and there's no point in hacking on the very soon to be obsolete BlueZ 4 stack.
Comment 2 Matthias Clasen 2013-03-04 12:49:26 UTC 
moving off the 3.8 list, considering that it is depending on bluez 5 migration
Comment 3 Bastien Nocera 2016-02-01 15:39:19 UTC 
This isn't necessary anymore. The default adapter will only be visible when the Bluetooth panel is opened, and any changes to the other adapters can be done via the command-line if the user wishes. As we only handle a single Bluetooth adapter in the UI, this is the easiest course of action.