Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1574501

Summary: firefox doesn't pick up locale on the first run
Product: Red Hat Enterprise Linux 7 Reporter: Jiri Prajzner <jprajzne>
Component: firefoxAssignee: Martin Stransky <stransky>
Status: CLOSED WORKSFORME QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.5CC: tpelka
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-11 09:55:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1556893    

Description Jiri Prajzner 2018-05-03 12:37:26 UTC
Description of problem:
firefox doesn't pick up locale on the first run, it needs restart

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

How reproducible:
always

Steps to Reproduce:
1. set locale via LC_ALL
2. start firefox
3.

Actual results:
firefox starts with new locale

Expected results:
firefox has to be restarted to pick up new locale

Additional info:

Comment 2 Martin Stransky 2018-05-03 17:03:11 UTC
Direct modification of "intl.locale.requested" fixes that - Firefox picks selected language for the first run. We may consider to remove the extension hacks here as WebExtension should not affect browser performance.

Comment 4 Martin Stransky 2018-05-07 07:51:32 UTC
(In reply to Martin Stransky from comment #2)
> Direct modification of "intl.locale.requested" fixes that - Firefox picks
> selected language for the first run. We may consider to remove the extension
> hacks here as WebExtension should not affect browser performance.

I was wrong here, intl.locale.requested solves nothing and we don't have a fix for that right now.

Comment 5 Tomas Pelka 2018-05-07 08:06:17 UTC
Seems it it fixed with firefox-60.0-2.el7_5

Comment 6 Martin Stransky 2018-05-07 08:40:05 UTC
(In reply to Tomas Pelka from comment #5)
> Seems it it fixed with firefox-60.0-2.el7_5

I don't believe so, the bug is just less visible here. I already updated the errata about this bug.

Comment 7 Martin Stransky 2018-05-07 10:51:09 UTC
Filed as https://bugzilla.mozilla.org/show_bug.cgi?id=1459575

Comment 8 Martin Stransky 2018-05-11 09:55:57 UTC
We use a distribution directory for extension which does not have this bug. Closing now as it affects internal builds only.

Comment 9 Tomas Pelka 2018-05-11 10:46:52 UTC
So If I understand it correctly there are two workarounds but we don't wan't to implement and maintain any of them?

I do admit this is definitely not a blocking issue and LANG should be take in account on second and following starts. 

But I bet there will be bug reports coming from customers confused by this race condition/regression.

Please reconsider.

Comment 10 Martin Stransky 2018-05-11 11:11:48 UTC
(In reply to Tomas Pelka from comment #9)
> So If I understand it correctly there are two workarounds but we don't wan't
> to implement and maintain any of them?

No, we will ship langpacks in distribution directory now so we won't have this issue any more.