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 695678 - UI for Name and Visibility seems confusing
UI for Name and Visibility seems confusing
Status: RESOLVED DUPLICATE of bug 693701
Product: gnome-control-center
Classification: Core
Component: Privacy
git master
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-12 04:01 UTC by Jim Campbell
Modified: 2013-04-22 09:21 UTC
See Also:
GNOME target: ---
GNOME version: 3.7/3.8

Attachments
privacy - options for showing or not showing the person's name. (17.26 KB, image/png)
2013-03-12 04:01 UTC, Jim Campbell 		Details

Description Jim Campbell 2013-03-12 04:01:44 UTC 
Created attachment 238664 [details]
privacy - options for showing or not showing the person's name.

The UI for the Name and Visibility seems confusing. To view the current setup, see: settings > privacy > name and visibility > stealth mode  

How is stealth mode in the privacy panel different than just turning off both of the name display options?

Also, turning stealth mode "on" will hide your name in both the regular screen and in the lock screen, but if you want to hide your name using the two individual options, you set the options to "off".

Is "stealth mode" necessary?  If you want to keep it, should the UI strings be set to read, "Hide your name in the top bar" / "Hide your name in the lock screen" and the slider behavior changed in a similar fashion?

See attached for the current behavior.
Comment 1 Allan Day 2013-03-12 12:23:39 UTC 
Dupe of bug 693701?
Comment 2 Bastien Nocera 2013-04-22 09:21:09 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 693701 ***