Bug 529853 - Exception: update.locale file doesn't exist in either the XCurProcD or GreD directories
Summary: Exception: update.locale file doesn't exist in either the XCurProcD or GreD d...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xulrunner
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-20 13:19 UTC by Michal Hlavinka
Modified: 2018-04-11 11:40 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-10-21 06:53:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Hlavinka 2009-10-20 13:19:45 UTC
Description of problem:

Firefox once a while adds this error message in error console log:

Error: [Exception... "update.locale file doesn't exist in either the XCurProcD or GreD directories"  nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame :: file:///usr/lib64/xulrunner-1.9.1/components/nsUpdateService.js :: getLocale :: line 549"  data: no]
Source File: file:///usr/lib64/xulrunner-1.9.1/components/nsUpdateService.js
Line: 549



Version-Release number of selected component (if applicable):
firefox-3.5.3-1.fc11.x86_64
xulrunner-1.9.1.3-1.fc11.x86_64

I'm getting these messages also in rawhide.

How reproducible:
100 %

Steps to Reproduce:
1.use firefox for some time
2.open error console
3.
  
Actual results:
exception messages in log

Expected results:
no exception message in log

Additional info:

Comment 1 Matěj Cepl 2009-10-24 19:37:56 UTC
Yes,

I have the same errors with xulrunner-1.9.1.3-1.fc12.x86_64:

Error: [Exception... "update.locale file doesn't exist in either the XCurProcD or GreD directories"  nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame :: file:///usr/lib64/xulrunner-1.9.1/components/nsUpdateService.js :: getLocale :: line 549"  data: no]
Source File: file:///usr/lib64/xulrunner-1.9.1/components/nsUpdateService.js
Line: 549

Comment 2 Martin Stransky 2009-11-12 08:49:47 UTC
Yes, I can see it...

Comment 3 Bug Zapper 2009-11-16 13:53:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Matěj Cepl 2009-12-21 11:52:33 UTC

*** This bug has been marked as a duplicate of bug 499982 ***

Comment 5 Michal Hlavinka 2010-01-13 15:06:11 UTC
reopened, because duplicate was closed as insufficient_data and I can't provide information requested in that bug (I've never seen any crashes related to the exception information in console). I guess the other bug contains two issues mixed together.

Comment 6 BlaiseP 2010-02-11 16:29:28 UTC
Attempting to set up for this bug.  firefox -g complains bitterly via ddd

No package /usr/lib/debug/.build-id/e7/51f768c3bed428ed8f5ae5ee0acff53f6280cf.debug available.

Comment 7 BlaiseP 2010-02-12 15:56:09 UTC
-the simple cure, after looking at the JavaScript

sudo touch /usr/lib/firefox-3.5.6/update.locale

Comment 8 Paul 2010-04-24 07:49:33 UTC
The simple cure works until you update firefox with yum again.  The old installation directory is then left with just the update.locale file and the new directory does not have the update.locale file.

Every firefox update I see the javascript errors in the console and I have to solve the same problem all over again.  Normally I forget where the little file was that I had to touch and end up finding the answer on the mozilla site all over again.

I'm guessing its not as simple as just the rpm touching this file for us when it installs?

Ubuntu seems to have a similar bug entry where if i read it correctly they thought upstream could fix it and then gave up. https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/411691

However an automatic workaround that doesn't require the user to touch files would be nice.

Comment 9 Bug Zapper 2010-11-04 09:21:05 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Michal Hlavinka 2010-11-04 16:03:01 UTC
problem still exists in F-14

Comment 11 Martin Stransky 2011-10-21 06:53:22 UTC
Should be already fixed in rawhide, please reopen if not.


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