Bug 757277

Summary:	Time display changes from set format after running application as su - in terminal
Product:	[Fedora] Fedora	Reporter:	Daniel Belton <danielbelton>
Component:	gnome-shell	Assignee:	Owen Taylor <otaylor>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	browning48ky, fgrose, maxamillion, otaylor, samkraju, vmclark, 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:	2012-02-02 20:07:32 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 Daniel Belton 2011-11-26 05:21:49 UTC

Description of problem:

I have Gnome shell set to display My time with the date and in 12 hours (AM/PM) format.

However after I run any application in the terminal window as root (su -) the time display switches to no date and 24 hours format.

The time will then remain in the wrong format until I restart Gnome shell or reboot.

Version-Release number of selected component (if applicable):

Gnome shell 3.2.1-2


How reproducible:

Always. 


Steps to Reproduce:
1. Open terminal window
2. su - to switch to root user shell
3. run any application (nautilus and gedit for certain do it.)
  
Actual results:

Time display will change from set format to displaying no date and 24 hour format

Expected results:

Time display to remain as I have it set. Displaying date and in 12 hour format

Additional info:

Comment 1 Vern Clark 2011-12-20 22:02:31 UTC

I didn't have this problem until I toggled Advance Settings : Desktop, have file manager handle the desktop = ON.

Now the problem persists no matter what.

Comment 2 Daniel Belton 2012-02-02 20:06:55 UTC

Not exactly certain which update corrected this issue, but I am no longer seeing it. 

I am going to close this bug and if it re-occurs, I will open a new one.