Bug 958066 - [gu_IN][control-center] - Calender data is showing in different locale when login with some other.
Summary: [gu_IN][control-center] - Calender data is showing in different locale when l...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 19
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-30 10:16 UTC by Sweta Kothari
Modified: 2015-04-21 04:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 15:06:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screen shot for the unusual error described in the bug (393.66 KB, image/jpeg)
2013-04-30 10:16 UTC, Sweta Kothari
no flags Details

Description Sweta Kothari 2013-04-30 10:16:27 UTC
Created attachment 741818 [details]
screen shot for the unusual error described in the bug

Description of problem: 


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

control-center-3.8.1-2.fc19.x86_64
How reproducible:


Steps to Reproduce:
1. Install F19 in Hindi locale
2. Post installation, create user, login with new user, in hindi locale
3. Change language with gu_IN(Gujarati) from system-config-language
4. Logout and login again in gu_IN locale with new user
5. Left click on system Calender from the panel
6  Observe the language in the calender itself.
  
Actual results:
The calender is showing Date format field strings in hindi when login with gu_IN locale.

Expected results:
It should show the Date format fields in gu_IN (Gujarati) locale itself, when logged in in Gujatari locale.


Special Observation :
With the command "locale" from the command line executed, its providing the following information which looks not correct.
Output :
LANG=gu_IN.utf8
LC_CTYPE="gu_IN.utf8"
LC_NUMERIC=hi_IN.UTF-8
LC_TIME=hi_IN.UTF-8
LC_COLLATE="gu_IN.utf8"
LC_MONETARY=hi_IN.UTF-8
LC_MESSAGES="gu_IN.utf8"
LC_PAPER=hi_IN.UTF-8
LC_NAME="gu_IN.utf8"
LC_ADDRESS="gu_IN.utf8"
LC_TELEPHONE="gu_IN.utf8"
LC_MEASUREMENT=hi_IN.UTF-8
LC_IDENTIFICATION="gu_IN.utf8"
LC_ALL=

Additional info:
Screen shot attached with a yellow circle pointed out the error.

Comment 1 Fedora End Of Life 2015-01-09 18:00:27 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-02-17 15:06:44 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.