http://bugs.winehq.org/show_bug.cgi?id=29387
Bug #: 29387 Summary: error while loading extensions in Chromium extension developer mode Product: Wine Version: 1.3.32 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: fracting@gmail.com Classification: Unclassified
Created attachment 38041 --> http://bugs.winehq.org/attachment.cgi?id=38041 Log: load extension in developer mode
1. Download and install chromium mini_installer from http://commondatastorage.googleapis.com/chromium-browser-continuous/Win/1141...
sha1sum: mini_installer-114191-2011-12-13-e49584228baf8d172726b9ee9dffd9acba1c9cde.exe
2. start chrome.exe with --no-sandbox
3. * Download np-activex from https://clients2.googleusercontent.com/crx/download/OAAAAK8kxCAvzc4RdlgO-6Fu... ( or http://bugs.winehq.org/attachment.cgi?id=37471 )
* rename extension_1_3_7.crx to extension_1_3_7.zip
* unzip extension_1_3_7.zip to a directory (let's name it np-activex/ )
* load np-activex/ with developers mode in 'chrome://extensions'
Expect result: load the extension
Actual result: an error message says:
"[8:9:50674:ERROR:extension_error_reporter.cc(56)] Extension error: Could not load extension from 'C:\users\fracting\My Documents\Wine\npactivex'. The 'manifest_version' key must be present and set to 2 (without quotes). "
Fail to load the extension.
http://bugs.winehq.org/show_bug.cgi?id=29387
--- Comment #1 from fracting fracting@gmail.com 2011-12-19 23:19:12 CST --- doesn't affect mini_installer-109801-20111112-02a25d3c293bc836c233e6a12ff57673.exe with wine-1.3.32
affects mini_installer-114191-2011-12-13-e49584228baf8d172726b9ee9dffd9acba1c9cde.exe with wine-1.3.32, wine-1.3.34 and wine-1.3.35
doesn't affect ChromeStandaloneSetup-d1d1067ccb19b1769a67e4c04062a997ad5751c8-2011-12-20.exe
http://bugs.winehq.org/show_bug.cgi?id=29387
fracting fracting@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://commondatastorage.go | |ogleapis.com/chromium-brows | |er-continuous/Win/114191/mi | |ni_installer.exe
http://bugs.winehq.org/show_bug.cgi?id=29387
fracting fracting@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=29078
http://bugs.winehq.org/show_bug.cgi?id=29387
Qian Hong fracting@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #2 from Qian Hong fracting@gmail.com 2012-01-26 11:13:17 CST --- Sorry, this report is invalid, my bad:
1. In chrome/common/extensions/extensions.cc: --- snip --- if (flags & REQUIRE_MODERN_MANIFEST_VERSION && manifest_version() < kModernManifestVersion && !CommandLine::ForCurrentProcess()->HasSwitch( switches::kAllowLegacyExtensionManifests)) { *error = ASCIIToUTF16(errors::kInvalidManifestVersion); return false; } --- snip ---
In chrome/common/extensions/extension_constants.cc: --- snip --- const char kInvalidManifestVersion[] = "The 'manifest_version' key must be present and set to 2 (without quotes)."; --- snip ---
The new chromium browser requires a new extension manifest file, this error is by design.
In chrome/common/chrome_switches.cc: --- snip --- const char kAllowLegacyExtensionManifests[] = "allow-legacy-extension-manifests"; --- snip ---
A "--allow-legacy-extension-manifests" switcher could avoid this error
2. Same behaviors on Windows with same chromium version.
http://bugs.winehq.org/show_bug.cgi?id=29387
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Austin English austinenglish@gmail.com 2012-01-28 14:04:19 CST --- Closing.
-
wine-bugs＠winehq.org