Bug 691183

Summary: No distinction between user and system settings
Product: [Fedora] Fedora Reporter: Christoph Wickert <cwickert>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: maxamillion, otaylor, samkraju, walters, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-27 18:15:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Christoph Wickert 2011-03-27 11:32:03 UTC
Description of problem:
gnome-shell does not distinguish between per-user and system-wide settings.

Version-Release number of selected component (if applicable):
gnome-shell-2.91.91-2.fc15.i686

How reproducible:
always

Steps to Reproduce:
1. Log into gnome-shell
2. Go to 'Activities' to display the search field
3. Type 'Language' into the search field
  
Actual results:
Both 'Language and Region' (per-user setting) and 'Language' (system-wide setting, system-config-language) are shown under settings. Now guess which one is the one you need.

Expected results:
There should be a way to distinguish between system-wide and per-user settings.

Additional info:
Same problem with control-center, also mixing system-wide and per-user settings.

Comment 1 Colin Walters 2011-03-27 18:15:23 UTC
In the next release, system-config-language will just be an application, while only the control-center components appear under Settings.

The system/user distinction has never really existed consistently; the design goal is to make things that one has privilege to change obviously done through the UI, such as changing the Date/Time can be done by clicking on the clock directly.

Please retest with 2.91.93 when it lands.

Comment 2 Colin Walters 2011-03-27 18:52:11 UTC
See also bug 685142