If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

chrome.manifest inside major language packages contains entry pointing to non-existent manifest 'chrome/<language>.manifest'

NEW
Unassigned

Status

()

Toolkit
Build Config
--
minor
6 years ago
6 years ago

People

(Reporter: Alfredo Fernández Díaz, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

6 years ago
User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; es-ES; rv:1.8.1.19) Gecko/20081212 SeaMonkey/1.1.14 (PmW)
Build Identifier: Gecko/20110611 SeaMonkey/2.1

After installing language packs to SeaMonkey 2.1, a quick peek at the error console after startup reveals several messages (exactly one per language pack installed) logged in this fashion:

Could not find jar manifest entry 'chrome/<locale code>.manifest'.

Tested with de, en-GB, es-ES, ja and ru so far, but I couldn't select more than one for this report.

Reproducible: Always

Steps to Reproduce:
1.Install a language pack to SeaMonkey.
2.Restart SeaMonkey
3.Have a look at the error console.

Actual Results:  
I see the described errors logged to the console. Everything else seems to work without problems.

Expected Results:  
Not to get any errors.

If you get into the installed <language pack>.xpi file, there's a file called chrome.manifest inside; in all of the offending language packs it contains a line that reads

"manifest chrome/es-ES.manifest"

or whatever language it is, while there's no such file inside the XPI file. Removing the line makes the corresponding error not to be logged at startup, but I'm not sure whether this a fix for the problem or just for the symptom.
This may be an issue in SeaMonkey build configuration, since localizers don't prepare the manifest files themselves.
Assignee: rpmdisguise-otros → nobody
Component: es-ES / Spanish → Build Config
Product: Mozilla Localizations → SeaMonkey
QA Contact: build-config
Target Milestone: --- → seamonkey2.3
Version: unspecified → SeaMonkey 2.1 Branch

Updated

6 years ago
Target Milestone: seamonkey2.3 → ---
Confirming:
/pub/seamonkey/nightly/2012/02/2012-02-06-00-30-31-comm-central-trunk-l10n/win32/xpi
seamonkey-2.10a1.fr.langpack.xpi
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: SeaMonkey 2.1 Branch → Trunk
Firefox would seem to have the same issue:
/pub/firefox/nightly/2012/02/2012-02-07-03-11-36-mozilla-central-l10n/win32/xpi
firefox-13.0a1.be.langpack.xpi

Alfredo, can you try and confirm?
(Reporter)

Comment 4

6 years ago
Yes, of course; it's been there at least from FireFox 6 (sorry I haven't anything older installed). I planned to report it for FireFox as a duplicate of this one, but then forgot, sorry. Could you please do it?
Component: Build Config → Build Config
Product: SeaMonkey → Core
QA Contact: build-config → build-config
Component: Build Config → Build Config
Product: Core → Toolkit
You need to log in before you can comment on or make changes to this bug.