543169 - Minefield and Jetpack don't play well together.

Status: RESOLVED WONTFIX

(Mozilla Labs :: Jetpack Prototype, defect)

Description

[Brian Carpenter [:geeknik]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a1pre) Gecko/20100129 Firefox/3.7a1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a1pre) Gecko/20100129 Firefox/3.7a1pre

I understand that Jetpack 0.7 is for Firefox 3.6, but after I force install Jetpack 0.7 with the Nightly Tester Tools, I can visit the Jetpack Gallery and install Jetpacks and I can also go to about:jetpack and see everything that is there, however, none of the Jetpacks actually run. 

Reproducible: Always

Comment 1

[Brian Carpenter [:geeknik]]

I installed Jetpack 0.8rc1 and it worked fine until OOPP caused a browser hang and I had to kill the browser processes. Once I restarted Minefield, the only thing that worked was about:jetpack. I couldn't install any Jetpacks and none of the currently installed Jetpacks worked. Just for those that might ask, I grabbed Jetpack 0.8rc1 from a link Daniel Buchner posted @ http://groups.google.com/group/mozilla-labs-jetpack/browse_thread/thread/5ac896a946210bdb.

Comment 2

[chris hofmann]

sounds like the fix for this might be in the new OOPP code, but we should figure that out and get jetpack working on the trunk again.

Comment 3

[chris hofmann]

might be a dupe of bug 517438

Comment 4

[Paul O'Shannessy [:zpao] (not bugmail, email directly)]

Brian, can you paste the following into your error console and see what it outputs? If it's more than just "Firefox" then there is a good chance this is a dupe. Otherwise, it's a different a problem.

Components.classes["@mozilla.org/fuel/application;1"].getService(Components.interfaces.fuelIApplication).name

Comment 5

[Brian Crowder]

For me, in a current nightly, it prints only "Firefox"

Comment 6

[Brian Carpenter [:geeknik]]

It just says Firefox for me as well. We'll see tomorrow if bug 517438 fixes this or not. :)

Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a1pre) Gecko/20100201 Firefox/3.7a1pre

Comment 7

[Paul O'Shannessy [:zpao] (not bugmail, email directly)]

If it says "Firefox" then this isn't the same bug.

Anybody see errors in your console when starting that might give us some clues as to what's actually happening?

Comment 8

[Brian Carpenter [:geeknik]]

These 2 things jump out at me on startup in the Error Console:

Error: Sorry, a required binary component for Jetpack isn't currently available for your operating system (WINNT_x86-msvc) and platform (Gecko 1.9.3).
Source File: file:///C:/Users/brian/AppData/Roaming/Mozilla/Firefox/Profiles/exg6zcyl.default/extensions/[e-mail]/components/stub.js
Line: 29

Failed to load XPCOM component: C:\Users\brian\AppData\Roaming\Mozilla\Firefox\Profiles\exg6zcyl.default\extensions\[e-mail]\platform\WINNT_x86-msvc\components\portaudio_x86.dll

Comment 9

[David Dahl :ddahl]

(In reply to comment #2)
> sounds like the fix for this might be in the new OOPP code, but we should
> figure that out and get jetpack working on the trunk again.

Jetpack never really worked on trunk, out of the box. If you build the binary component yourself by checking out the source from labs' hg repo and doing "python manage.py xpcom" with the correct paths to your obj dir and source dir, you will have a component that works.

Comment 10

[Daniel Buchner [:dbuc]]

We will be monitoring all these issues after the rebooted Jetpack code base is released in the first week of March to ensure their causes are not duplicated. Many of the bugs/issues with the prototype version of Jetpack will be made irrelevant given the structure of the new SDK.