qbrt fails to start

[benfrancis]

STR:

• npm install -g qbrt
• qbrt run https://eggtimer.org/

Error:

JavaScript error: file:///home/tola/.nvm/versions/node/v8.11.3/lib/node_modules/qbrt/dist/linux/runtime/qbrt/components/DisabledAddonManager.js, line 24: TypeError: XPCOMUtils.generateQI is not a function
JavaScript error: file:///home/tola/.nvm/versions/node/v8.11.3/lib/node_modules/qbrt/dist/linux/runtime/qbrt/components/DisabledTelemetryStartup.js, line 14: TypeError: XPCOMUtils.generateQI is not a function
JavaScript error: file:///home/tola/.nvm/versions/node/v8.11.3/lib/node_modules/qbrt/dist/linux/runtime/qbrt/components/CommandLineHandler.js, line 42: TypeError: XPCOMUtils.generateQI is not a function

Tested on Ubuntu 18.04 LTS.

[patrickalima98]

Same problem here
STR:

• npm i -g qbrt
• qbrt run https://eggtimer.org/

Error:

JavaScript error: file:///C:/Users/patri/AppData/Roaming/npm/node_modules/qbrt/dist/win32/runtime/qbrt/components/DisabledAddonManager.js, line 24: TypeError: XPCOMUtils.generateQI is not a function
JavaScript error: file:///C:/Users/patri/AppData/Roaming/npm/node_modules/qbrt/dist/win32/runtime/qbrt/components/DisabledTelemetryStartup.js, line 14: TypeError: XPCOMUtils.generateQI is not a function
JavaScript error: file:///C:/Users/patri/AppData/Roaming/npm/node_modules/qbrt/dist/win32/runtime/qbrt/components/CommandLineHandler.js, line 42: TypeError: XPCOMUtils.generateQI is not a function
JavaScript error: resource://gre/modules/ActorManagerChild.jsm, line 269: TypeError: singletons is null

Tested on Windows 10 x64 Version 1809

[rafaelmr2]

Same here in Manjaro.

[MattGyverLee]

Me too.

[MattGyverLee]

It's a Mozilla issue: mozilla/tls-canary#171

[lewisthoma5]

Windows 10 same issue.

[guilmour]

Same here in Debian 9.8 (stretch) 😿

• npm i -g qbrt

• qbrt run https://eggtimer.org/

JavaScript error: file:///home/guilmour/.nvm/versions/node/v11.10.1/lib/node_modules/qbrt/dist/linux/runtime/qbrt/components/DisabledAddonManager.js, line 24: TypeError: XPCOMUtils.generateQI is not a function
JavaScript error: file:///home/guilmour/.nvm/versions/node/v11.10.1/lib/node_modules/qbrt/dist/linux/runtime/qbrt/components/DisabledTelemetryStartup.js, line 14: TypeError: XPCOMUtils.generateQI is not a function
JavaScript error: file:///home/guilmour/.nvm/versions/node/v11.10.1/lib/node_modules/qbrt/dist/linux/runtime/qbrt/components/CommandLineHandler.js, line 42: TypeError: XPCOMUtils.generateQI is not a function

Someone did get success on troubleshooting this issue?

[star-buck]

same on debian buster... can a fix be deployed for qrbt similar to that in the ticket above?

[guilmour]

@star-buck I tried that, but now I'm stuck at the error:

JavaScript error: file:///home/guilmour/gits/qbrt6/components/CommandLineHandler.js, line 28: NS_ERROR_FILE_NOT_FOUND: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIChannel.open2]

:/

[nothingismagick]

Same on MacOS

[dragondaksh]

Still the issue persists, please can someone tell what can be done?

[star-buck]

Would love to see that fixed as well. Otherwise qbrt is useless?

[benfrancis]

I am totally out of my depth here, but let's see where we can get with this. These errors are being generated by:

• DisabledAddonManager.js
• DisabledTelemetryStartup.js
• CommandLineHandler.js

These are all in qbrt's components directory and to my untrained eye appear to be designed to stub out components that aren't used by qbrt but that Firefox (being used as a runtime) somehow expects to be there.

The errors appear to be caused by calls these components make to an XPCOMUtils.generateQI() method which no longer exists. Thunderbird apparently had the same problem and they solved it by "providing their own little generateQI implementation", which @cr didn't seem to like.

If I comment out the lines in those components which call XPCOMUtils.generateQI() (which removes the QueryInterface property of an object in each case) then XPCOMUtils.jsm complains that QueryInterface doesn't exist. Which I assume is why it's there in the first place!

JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 458: TypeError: this._instance.QueryInterface is not a function
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 458: TypeError: this._instance.QueryInterface is not a function
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 433: TypeError: (new component(...)).QueryInterface is not a function

...and that is as far as I have got.

[benfrancis]

I note that mozilla/tls-canary#172 fixed a similar error by replacing instances of XPCOMUtils.generateQI() with ChromeUtils.generateQI().

If I do this for qbrt I no longer get the error messages above, I get a new error:

error starting runtime: [Exception... "Component does not have requested interface" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: resource://qbrt/modules/Runtime.jsm :: getOuterWindowID :: line 176" data: no]

Progress..?

[benfrancis]

Note: The above is the error I get when trying to run my own application with the qbrt runtime with qbrt run ./

If I try to run the eggtimer example as in the STR at the top of this issue (qbrt run https://eggtimer.org/), a blank window is opened but I see a different error on the command line:

JavaScript error: chrome://global/content/elements/browser-custom-element.js, line 874: TypeError: aParams is null