392437 - Components are missing in SeaMonkey 2.0apre1 on Linux

Status: RESOLVED DUPLICATE of bug 366673

(SeaMonkey :: General, defect)

Description

[Johannes Walther]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9a8pre) Gecko/2007081501 SeaMonkey/2.0a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9a8pre) Gecko/2007081501 SeaMonkey/2.0a1pre

While being there in past versions and available in SeaMonkey 2.0apre1 on Windows, Password Manager (dialogue), Chatzilla and Venkman are missing for trunk since migration to XULRunner on Linux.
Especially the missing UI interface to Password Manager is a big obstacle. It neither shows up in Tools menu nor in Preferences/Privacy & Security.

Reproducible: Always

Comment 1

[Mark Banner (:standard8)]

(In reply to comment #0)
> Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9a8pre)
> Gecko/2007081501 SeaMonkey/2.0a1pre

So you're using a de-DE build, not an en-US build? I'm guessing download manager may be missing as well (though Robert can probably correct me on that one).

I think you're hitting on of the following:

* bug 286110 and its blockers - which will stop the items you mentioned working in localized builds.
* bug 366673 which I believe will again stop the items working (for all langauges including en-US) if you have everything read-only to the user you are running with.

Comment 2

[Robert Kaiser]

Localized builds are not yet supported, and things like password manager/wallet stuff missing is directly caused by bug 286110 and its blockers, i.e. that localized builds are not supported.

Additionally, de-DE is an invalid locale code for trunk.

All that makes this an invalid bug report.

Comment 3

[Johannes Walther]

No sorry, I'm not using a localized build. It's a standard nightly directly from mozilla.org, no localizations installed.
The de-DE in the browser string is due to a
user_pref("general.useragent.locale", "de-DE"); in user.js.

Comment 4

[Robert Kaiser]

well, that setting should never be set in the first place, and I'll probably regard all reports made with that setting as invalid.
Anyways, in this case this is a build you installed as root without write permissions for a normal user, never launched as root, but are using as a normal user, which makes us show what you said in comment 0. We need at least one run with write permissions to the chrome/ directory until all dependencies on bug 366673 are fixed.

In this case, this is a dupe of bug 366673, actually.

Comment 5

[Mark Banner (:standard8)]

(In reply to comment #4)
> We need at least
> one run with write permissions to the chrome/ directory until all dependencies
> on bug 366673 are fixed.

Or I think you can just run ./seamonkey -register as root once on install (until bug 366673 is fixed)