Bug 757277 - Time display changes from set format after running application as su - in terminal
Summary: Time display changes from set format after running application as su - in ter...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-26 05:21 UTC by Daniel Belton
Modified: 2012-02-02 20:07 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-02 20:07:32 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.